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 15:34:29
Message-ID: 15655.1250091269@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:
> Tom Lane wrote:
>> Well, I meant pseudo-backend in the sense of "just like an AV worker".
>> We might not want it to show in pg_stat_activity, but otherwise I think
>> it'd be the same.

> Hmm, to what database would it connect?

Well, it wouldn't. As of the patch I'm working on, it's okay to have
PGPROC entries showing zero in databaseId. Normally they'd be backends
that weren't done starting yet, but I see no reason the AV launcher
couldn't stay that way indefinitely.

This would likely mean that the only thing it could safely do is seqscan
pg_database, but that's all we need anyway, no?

I suppose it might be a bit ugly to refactor InitPostgres enough to
support this. I'm not sure which parts of that code we'd actually need
to have run.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Csaba Nagy 2009-08-12 15:40:38 Re: machine-readable explain output v4
Previous Message Mike 2009-08-12 15:32:45 Re: machine-readable explain output v4