Skip site navigation (1) Skip section navigation (2)

Re: BUG #6041: Unlogged table was created bad in slave node

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Emanuel <postgres(dot)arg(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6041: Unlogged table was created bad in slave node
Date: 2011-06-07 15:50:23
Message-ID: 14416.1307461823@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)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(at)mail(dot)gmail(dot)com>.

However, I don't like where you put the execution-time test there.  I'd
put it in ExecOpenScanRelation instead, so that it covers both seqscan
and indexscan accesses.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2011-06-07 15:56:45
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch
Previous:From: Heikki LinnakangasDate: 2011-06-07 15:36:29
Subject: Re: WALInsertLock tuning

pgsql-bugs by date

Next:From: Andres FreundDate: 2011-06-07 17:42:46
Subject: Re: BUG #6041: Unlogged table was created bad in slave node
Previous:From: Daniel Cristian CruzDate: 2011-06-07 15:43:37
Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group