Re: Re: xReader, double-effort (was: Temporary tables under hot standby) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: xReader, double-effort (was: Temporary tables under hot standby)
Date
Msg-id CA+TgmoYmbf5RRdQv7+fFVi-ELos0sarn6yxHomqx2jvV9_2s=Q@mail.gmail.com
Whole thread Raw
In response to Re: Re: xReader, double-effort (was: Temporary tables under hot standby)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Apr 29, 2012 at 11:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Sun, Apr 29, 2012 at 6:00 PM, Hannu Krosing <hannu@2ndquadrant.com> wrote:
>>> So you basically need a large part of postgres for reliably making sense
>>> of WAL.
>
>> Agreed, but I think that's a problem we need to fix and not a
>> tolerable situation at all.  If a user can create a type-output
>> function that goes and looks at the state of the database to determine
>> what to output, then we are completely screwed, because that basically
>> means you would need to have a whole Hot Standby instance up and
>> running just to make it possible to run type output functions.
>
> You mean like enum_out?  Or for that matter array_out, record_out,
> range_out?

Yeah, exactly.  :-(

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: xReader, double-effort (was: Temporary tables under hot standby)
Next
From: Dave Page
Date:
Subject: Re: Future In-Core Replication