| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Difference in dump from original and restored database due to NOT NULL constraints on children |
| Date: | 2024-11-14 10:56:37 |
| Message-ID: | CAExHW5tbdgAKDfqjDJ-7Fk6PJtHg8D4zUF6FQ4H2Pq8zK38Nyw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Alvaro,
Because of the test I am developing under discussion at [1], I noticed
that the DDLs dumped for inheritance children with NOT NULL
constraints defer between original database and database restored from
a dump of original database. I investigated those differences, but can
not decide whether they are expected and whether they are intentional
or not. Look something related to
14e87ffa5c543b5f30ead7413084c25f7735039f.
I have attached four files. Original dumps from source (src_dump.sql)
and restored databases (dest_dump.plain.sql). Dumps adjusted for known
differences (src_dump.sql_adjusted and
dest_dump.plain.sql_adjusted respectively)
as per AdjustDump.pm module added by 0001 patch attached to [1].
Are these differences safe? Are they intentional?
--
Best Wishes,
Ashutosh Bapat
| Attachment | Content-Type | Size |
|---|---|---|
| dest_dump.plain.sql_adjusted | application/octet-stream | 491.2 KB |
| src_dump.sql | application/sql | 497.9 KB |
| src_dump.sql_adjusted | application/octet-stream | 491.1 KB |
| dest_dump.plain.sql | application/sql | 497.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2024-11-14 11:04:57 | Re: [PATCH] Refactor SLRU to always use long file names |
| Previous Message | Pavan Deolasee | 2024-11-14 10:48:02 | Potential ABI breakage in upcoming minor releases |