pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fourat Zouari <fourat@gmail.com>
To: Jim C. Nasby <jim@nasby.net>
Cc: Bricklen Anderson <banderson@presinet.com>
Cc: pgsql-novice@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: Copying data from table to table (cloned tables)
Date: Wed, 11 Oct 2006 13:30:22 +0200
Message-ID: <621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com> (raw)
In-Reply-To: <20061010153724.GI72517@nasby.net>
References: <621eda8a0610091651oc78994fy2b358260f5c9b58a@mail.gmail.com>
	<452AE2FF.1020409@presinet.com>
	<20061010152457.GG72517@nasby.net>
	<20061010153724.GI72517@nasby.net>

what's the benefits using a serialized trans ?

On 10/10/06, Jim C. Nasby <jim@nasby.net> wrote:
>
> On Tue, Oct 10, 2006 at 10:24:57AM -0500, Jim C. Nasby wrote:
> > > If you just want to copy the data across to the other table:
> > > begin;
> > > insert into table2 select * from table1 where <some criteria>;
> > > commit;
> > >
> > > if you also want to remove that same data from table1:
> > > begin;
> > > insert into table2 select * from table1 where <some criteria>;
> > > delete from table1 where <same criteria as above>;
> > > commit;
>
> I forgot to mention you could also use a serializable transaction with
> your method...
>
> BEGIN ISOLATION LEVEL SERIALIZABLE;
> INSERT ...
> DELETE ...
> COMMIT;
>
> Just remember you'll need to deal with the possibility of a 'could not
> serialize' error.
> --
> Jim Nasby                                            jim@nasby.net
> EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)
>

view thread (13+ messages)  latest in thread

Message-ID: <621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com>
Permalink:  ../621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com/
Also on:    postgresql.org/message-id/621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: fourat@gmail.com, jim@nasby.net, banderson@presinet.com, pgsql-novice@postgresql.org
  Subject: Re: Copying data from table to table (cloned tables)
  In-Reply-To: <621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com>
  References: <621eda8a0610091651oc78994fy2b358260f5c9b58a@mail.gmail.com> <452AE2FF.1020409@presinet.com> <20061010152457.GG72517@nasby.net> <20061010153724.GI72517@nasby.net> <621eda8a0610110430y5be06e22t27d6c99991e86dc8@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox