From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Vote on SET in aborted transaction |
Date: | 2002-04-25 03:11:51 |
Message-ID: | 3CC773F7.6FEA24D8@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > > >
> > > > What are you expecting for psql e.g. the following
> > > > wrong(?) example ?
> > > >
> > > > [The curren schema is schema1]
> > > > begin;
> > > > create schema foo;
> > > > set search_path = foo;
> > > > create table t1 (....); [error occurs]
> > > > commit;
> > > > insert into t1 select * from schema1.t1;
> > >
> > > I am expecting the INSERT will use the search_path value that existed
> > > before the error transaction began.
> > >
> >
> > So you see foo.t1 which is a copy of schema1.t1
> > if all were successful and you may be able to see
> > the doubled schema1.t1 in case of errors.
>
> Yes, I think that is how it would behave. If you don't roll back 'set
> search_path', you are pointing to a non-existant schema.
OK I see your standpoint. If Tom agrees with Bruce I don't
object any more.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Curt Sampson | 2002-04-25 03:19:14 | Re: Sequential Scan Read-Ahead |
Previous Message | Bruce Momjian | 2002-04-25 03:03:08 | Re: Vote on SET in aborted transaction |