Re: Re: xReader, double-effort (was: Temporary tables under hot standby)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Andres Freund <andres(at)2ndquadrant(dot)com>, Aakash Goel <aakash(dot)bits(at)gmail(dot)com>, Josh Berkus <josh(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: xReader, double-effort (was: Temporary tables under hot standby)
Date: 2012-04-30 03:33:28
Message-ID: CA+TgmoYmbf5RRdQv7+fFVi-ELos0sarn6yxHomqx2jvV9_2s=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 29, 2012 at 11:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sun, Apr 29, 2012 at 6:00 PM, Hannu Krosing <hannu(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2012-04-30 06:35:02 Re: Future In-Core Replication
Previous Message Tom Lane 2012-04-30 03:29:32 Re: Re: xReader, double-effort (was: Temporary tables under hot standby)