Re: Potential bug in pg_dump ...

From: Brent Verner <brent(at)rcfile(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Potential bug in pg_dump ...
Date: 2002-01-12 02:10:04
Message-ID: 20020112021004.GA16489@rcfile.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[2002-01-11 18:30] Tom Lane said:
| Brent Verner <brent(at)rcfile(dot)org> writes:
| > Attached is a patch that implements table locking for pg_dump.
|
| Checked and applied, with some small tweaking. I broke the outer loop
| of getTables() into two loops, one that extracts data from the pg_class
| SELECT result and locks the target tables, and a second one that does
| the rest of the stuff that that routine does. This is to minimize the
| time window between doing the pg_class SELECT and locking the tables.

ACK. Now I understand what you meant by the "more than zero time"
to lock the tables :-)

thanks.
brent

--
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing." -- Duane Allman

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2002-01-12 03:53:08 checkpoint hang in 7.2b4
Previous Message Tom Lane 2002-01-11 23:30:11 Re: Potential bug in pg_dump ...