Re: WIP: getting rid of the pg_database flat file - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: WIP: getting rid of the pg_database flat file
Date
Msg-id 20090812014226.GQ16362@alvh.no-ip.org
Whole thread Raw
In response to WIP: getting rid of the pg_database flat file  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP: getting rid of the pg_database flat file  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> To actually get rid of the pg_database flat file, we'd need to take the
> further step of teaching the AV launcher to read pg_database for itself,
> or else refactor things so that the AV workers can do that for it.
> (Alvaro, any comments about the best way to proceed there?)

Hmm.  I don't see any easy way out of that at the moment ... the
launcher would have to become a pseudo-backend, at least to the point
where it is able to read pg_database.  I don't see how could workers
help the launcher with that, unless we made them write a flatfile
representation of pg_database, which would put us back where we started ...

I'll have a deeper look around.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: dependencies for generated header files
Next
From: Tom Lane
Date:
Subject: Re: Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)