Re: WIP: getting rid of the pg_database flat file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: WIP: getting rid of the pg_database flat file
Date: 2009-08-12 16:46:57
Message-ID: 20090.1250095617@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Are you going to commit the current patch? We can remove the hacks that
> support autovacuum later. I was thinking that InitPostgres could be
> split in two, with the first half ending just after
> RelationCacheInitializePhase2. Then workers could figure out their
> database names and go off on the second half; regular backends would
> just call the two halves directly. That way, the launcher could use the
> first half.

Yeah, I intend to commit what I have after I finish cleaning up a few
loose ends (just found a bug with CLOBBER_CACHE_ALWAYS), and then we
can take a look at making autovacuum play with it. I envision three
or four commits before flatfiles.c can disappear.

> (BTW I assume there is going to be an index on OID
> available on pg_database after the shared relcache initialization?)

Yeah. That's not in the patch I sent last night, but the OID index has
to become nailed too in order to allow removing FindMyDatabaseByOid.
However, I'm not sure that the AV launcher could touch it --- were
you thinking that would be important?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2009-08-12 17:08:32 Re: BUG #4961: pg_standby.exe crashes with no args
Previous Message Josh Berkus 2009-08-12 16:27:06 Re: Alpha 1 release notes