From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: COPY with no WAL, in certain circumstances |
Date: | 2007-01-06 19:06:36 |
Message-ID: | 15068.1168110396@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Euler Taveira de Oliveira <euler(at)timbira(dot)com> writes:
> Simon Riggs wrote:
>> The enclosed patch implements this, as discussed. There is no user
>> interface to enable/disable, just as with CTAS and CREATE INDEX; no
>> docs, just code comments.
>>
> IMHO, this deserves an GUC parameter (use_wal_in_copy?).
Why? The whole point is that it's automatic and transparent.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-06 19:40:06 | Re: xlog directory at initdb time |
Previous Message | Joshua D. Drake | 2007-01-06 19:01:21 | Re: COPY with no WAL, in certain circumstances |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-06 19:40:06 | Re: xlog directory at initdb time |
Previous Message | Joshua D. Drake | 2007-01-06 19:01:21 | Re: COPY with no WAL, in certain circumstances |