| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jim Nasby <jim(at)nasby(dot)net> |
| Subject: | Re: pg_restore --no-post-data and --post-data-only |
| Date: | 2011-12-07 16:31:21 |
| Message-ID: | 19777.1323275481@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>>> Note that this feature has the odd effect that some constraints are loaded at the same time as the tables and some are loaded with the post-data. This is consistent with how text-mode pg_dump has always worked, but will seem odd to the user. This also raises the possibility of a future pg_dump/pg_restore optimization.
>> That does seem odd. Why do we do it that way?
> Beats me.
Performance, mostly --- we prefer to apply checks during the original
data load if possible, but for indexes and FK constraints it's faster to
apply them later. Also, we can separate constraints from the original
table declaration if it's necessary to break a reference circularity.
This isn't something that would be wise to whack around.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Mead | 2011-12-07 16:45:41 | Re: IDLE in transaction introspection |
| Previous Message | Tom Lane | 2011-12-07 16:26:40 | Re: documentation issue - extensions |