| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Michael Loftis <mloftis(at)wgops(dot)com>, Jan Wieck <janwieck(at)yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vote on SET in aborted transaction |
| Date: | 2002-04-25 03:00:28 |
| Message-ID: | 3CC7714C.B3BE1061@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> Hiroshi Inoue 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.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-25 03:03:08 | Re: Vote on SET in aborted transaction |
| Previous Message | Bruce Momjian | 2002-04-25 02:59:41 | Re: Inefficient handling of LO-restore + Patch |