Alvaro Herrera <alvherre@surnet.cl> writes:
> On Tue, May 31, 2005 at 02:49:09PM -0400, Tom Lane wrote:
>> It's a rather lame attempt to ensure that you don't get a corrupt copy
>> due to the database changing while you copy it ... I'd like to find
>> a better way to do it ...
> You sounded less enthusiastic about it on january:
> http://archives.postgresql.org/pgsql-bugs/2005-01/msg00395.php
Well, I was expressing dissatisfaction with the obvious way of fixing
it. If we knew a low-overhead way to fix it I'd be much more
enthusiastic ...
regards, tom lane