Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I use pg_dump to dump a database with several tables with the same schema. When looking at the data I see it inserted it into the wrong table.
Version-Release number of selected component (if applicable):
8.4.8
How reproducible:
not sure
Steps to Reproduce:
1. create database with several tables with the same column schema.
2. pg_dump the database.
3. load it to a new database.
Actual results:
the data is not inserted to the right table.
Expected results:
restoration creates the same database.
Additional info:
I can provide the dump (it's very large) and the ip of the database I dumped.
Please provide a concrete test case. I've never heard of such behavior and cannot duplicate it here. The test case I tried is
create schema s1;
create table s1.t1 (f1 text);
insert into s1.t1 values ('schema s1');
create schema s2;
create table s2.t1 (f1 text);
insert into s2.t1 values ('schema s2');
create schema s3;
create table s3.t1 (f1 text);
insert into s3.t1 values ('schema s3');
and this dumps and restores just fine.