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

Re: CLONE TABLE DATA TO <new_table>

From: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CLONE TABLE DATA TO <new_table>
Date: 2012-01-13 13:25:22
Message-ID: C4DAC901169B624F933534A26ED7DF310861B2C3@JENMAIL01.ad.intershop.net (view raw or flat)
Thread:
Lists: pgsql-hackers
This would be great, but I can't C  :-(

Marc

> -----Original Message-----
> From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com]
> Sent: Freitag, 13. Januar 2012 14:12
> To: Marc Mamin
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] CLONE TABLE DATA TO <new_table>
> 
> On Fri, Jan 13, 2012 at 5:56 AM, Marc Mamin <M(dot)Mamin(at)intershop(dot)de>
> wrote:
> > I wonder if it would be possible to have a fast table clone function
> (data
> > only) while copying the corresponding data files
> >
> > instead of using the "CREATE TABLE AS"  way.
> >
> > pg_upgrade seems to have such a mechanisms, though it requires to
> first stop
> > the server...
> >
> > This would of course require to lock the complete table and ensure
> that all
> > latest changes are flushed to the plates.
> 
> I think it would be possible to implement this.  In fact, it could
> probably be done as a contrib module.
> 
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-01-13 13:27:38
Subject: Disabled features on Hot Standby
Previous:From: Robert HaasDate: 2012-01-13 13:12:16
Subject: Re: CLONE TABLE DATA TO <new_table>

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