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

AW: relation ### modified while in use

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: relation ### modified while in use
Date: 2000-11-03 14:05:27
Message-ID: 11C1E6749A55D411A9670001FA6879633680E3@sdexcsrv1.f000.d0188.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
> > The problem at hand is that
> > a plan may be invalidated before it is even finished building.  Do you
> > expect the parse-rewrite-plan-execute pipeline to be prepared to back up
> > and restart if we notice a relation schema change report halfway down the
> > process? 

Yes, during the processing "of one single statement", (and this includes
the parse/plan phase) we will need to hold a shared lock from the first access,
as by our previous discussion.

Andreas

pgsql-hackers by date

Next:From: Christof PetigDate: 2000-11-03 14:53:33
Subject: Re: Leaking definitions to user programs
Previous:From: Hiroshi InoueDate: 2000-11-03 13:51:26
Subject: RE: relation ### modified while in use

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