Re: BUG #6041: Unlogged table was created bad in slave node - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #6041: Unlogged table was created bad in slave node
Date
Msg-id BANLkTi=2ewL63njHx7mth1tV6_NYimAR9A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6041: Unlogged table was created bad in slave node  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #6041: Unlogged table was created bad in slave node
List pgsql-bugs
On Tue, Jun 7, 2011 at 11:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Patch along these lines attached.
>
> Frankly, I find this quite ugly, and much prefer the general approach of
> your previous patch in <BANLkTim433vF5HWjbJ0FSWm_-xA8DDaGNg@mail.gmail.co=
m>.
>
> However, I don't like where you put the execution-time test there. =A0I'd
> put it in ExecOpenScanRelation instead, so that it covers both seqscan
> and indexscan accesses.

Ah, OK.  I was wondering if there was a better place.  I'll do it that
way, then.

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

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #6041: Unlogged table was created bad in slave node
Next
From: Noah Misch
Date:
Subject: Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns