Re: Creation of temporary tables on read-only standby servers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Creation of temporary tables on read-only standby servers
Date
Msg-id 3738.1287606676@sss.pgh.pa.us
Whole thread Raw
In response to Re: Creation of temporary tables on read-only standby servers  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:
> On Wed, Oct 20, 2010 at 8:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think it's pointless to speculate about whether we might have divvied
>> up the meta-information about tables differently if we'd foreseen
>> wanting to do this. �It is what it is, and there is *way* too much code
>> depending on it, both inside the backend and in clients. �Any
>> reimplementation of temp tables will still have to expose largely the
>> same catalog information that exists for tables now. �We can probably
>> get away with marginal changes like redefining relfilenode, but we can't
>> avoid providing catalog entries that describe the schema and statistics
>> of a temp table.

> I agree about the schema -- that's the whole point of the catalog tables.

> I felt like the statistics were pretty marginal to begin with.

I'm thinking more of pg_statistic than the stuff in pg_class --- I agree
that we could probably kluge some other approach for relpages and
reltuples, but that doesn't scale to the real statistics.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: [PATCH] pgcrypto: Test for NULL before dereferencing pointer
Next
From: Greg Stark
Date:
Subject: Re: max_wal_senders must die