From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Naz Gassiep <naz(at)mira(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: dump / restore functionality |
Date: | 2006-09-12 14:40:42 |
Message-ID: | 16024.1158072042@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Naz Gassiep <naz(at)mira(dot)net> writes:
> At risk of being chastised for reviving old issues, I was wondering,
> what are the chances were of getting the dump / restore selectivity into
> 8.2 ?
None, but feel free to start coding for 8.3.
> I am referring to the idea that, instead of the current 2 parts, a
> dump could be broken up into 3 parts, namely tables, data and everything
> else, so that data from one dump could be mixed and matched with schema
> defs from another dump easily and scriptably.
That seems like a rather spectacular overstatement of the likely
benefits, not to mention a misdescription of what was discussed.
AFAIR what was discussed was separating
- schema stuff needed before loading data
- table data
- schema stuff needed after loading data
where the last category boils down to "indexes and then foreign keys".
All the "other stuff" such as functions really needs to be in the
first part ... or at least there's no visible benefit to delaying
loading it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-12 14:59:34 | Re: currentItemData & currentMarkData |
Previous Message | Naz Gassiep | 2006-09-12 14:31:59 | Re: dump / restore functionality |