Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: [HACKERS] What's left?


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
  • Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, "''Merlin Moncure' '" <merlin(dot)moncure(at)rcsonline(dot)com>, "'pgsql-hackers-win32 '" <pgsql-hackers-win32(at)postgreSQL(dot)org>
  • Subject: Re: [HACKERS] What's left?
  • Date: Mon, 26 Jan 2004 20:26:23 -0500
  • Message-id: <7829.1075166783@sss.pgh.pa.us> <text/plain>

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> In this way, no one ever has the rename file open while we are holding
> the locks, and we can loop without holding an exclusive lock on
> pg_shadow, and file writes remain in order.

You're doing this where exactly, and are certain that you are holding no
locks why exactly?  And if you aren't holding a lock, what prevents
concurrency bugs?

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group