From: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org, Alon Goldshuv <agoldshuv(at)greenplum(dot)com> |
Subject: | Re: WAL bypass for CTAS |
Date: | 2005-06-05 04:50:55 |
Message-ID: | 200506051450.56218.mr-russ@pws.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sun, 5 Jun 2005 10:29 am, Neil Conway wrote:
> Bruce Momjian wrote:
> > Well, it isn't going to help us for 8.1 because 8.0 will not have it,
> > and if we add the clause we make loading the data into previous releases
> > harder.
>
> pg_dump output in general is not compatible with prior releases. It
> would be a nice feature to have, but until we have it, I don't see that
> changing or not changing the COPY syntax will make a major difference to
> dump backward compatibility.
Don't we usually suggest using the new pg_dump to dump the old database anyway?
If that's the case, then we just add the locking options in there. Otherwise, yes you are
stuck with the original locking mechanism. But if people are smart and want faster loading
they will play with sed and friends to make it work.
Even if people for 8.1 just get the supposed 500% speed increase because of a better parser,
lots of people will be happy.
Regards
Russell Smith
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2005-06-05 04:51:36 | Re: Unicode characters above 0x10000 #2 |
Previous Message | Tom Lane | 2005-06-05 04:45:32 | Re: [HACKERS] WAL: O_DIRECT and multipage-writer (+ memory |
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2005-06-05 04:51:36 | Re: Unicode characters above 0x10000 #2 |
Previous Message | Tom Lane | 2005-06-05 04:45:32 | Re: [HACKERS] WAL: O_DIRECT and multipage-writer (+ memory |