| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump order of operation |
| Date: | 2018-08-26 18:18:35 |
| Message-ID: | d6d29967-bf13-ec40-99af-ae62d553955a@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/26/2018 10:24 AM, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>> In v8.4, I noticed that the tables seemed to be dumped in alphabetical
>> order. Not so much, though, in a multithreaded 9.6 dump of an 8.4 database;
>> there's no pattern that I can discern.
>> In what order does the 9.6 pg_dump dump tables?
> I don't believe the ordering rules have changed materially since 8.4;
> it's intended to be by object kind, and within that by name, except
> where dependencies force doing something else.
I thought that didn't matter, since FK and PK constraints were added (in the
required order) after all data was loaded).
> But what are you thinking constitutes the "dump order" in a parallel dump?
I don't understand your question.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-26 18:39:50 | Re: "cache lookup failed for type ####" when running unit tests |
| Previous Message | Wilhansen Li | 2018-08-26 17:40:19 | "cache lookup failed for type ####" when running unit tests |