| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: could not create directory "...": File exists |
| Date: | 2013-01-18 00:26:18 |
| Message-ID: | 20947.1358468778@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> This seems to provide a reasonably principled
>> argument why we might want to fix this case with a localized use of an
>> MVCC scan before we have such a fix globally.
> I had discussed that idea a bit with Andres on IRC and my only concern
> was if there's some reason that acquiring a snapshot during createdb()
> would be problematic. It doesn't appear to currently and I wasn't sure
> if there'd be any issues.
Don't see what. The main reason we've not yet attempted a global fix is
that the most straightforward way (take a new snapshot each time we
start a new SnapshotNow scan) seems too expensive. But CREATE DATABASE
is so expensive that the cost of an extra snapshot there ain't gonna
matter.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2013-01-18 00:33:21 | Re: Slave enters in recovery and promotes when WAL stream with master is cut + delay master/slave |
| Previous Message | Tomas Vondra | 2013-01-17 23:55:05 | Re: PATCH: optimized DROP of multiple tables within a transaction |