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

Re: Patch for pg_dump: Multiple -t options and new -T option

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,"David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>,pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for pg_dump: Multiple -t options and new -T option
Date: 2004-07-20 06:47:21
Message-ID: 40FCBFF9.5090601@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> Yes, the reason it would be nice for me is that currently if you want to 
> dump two specific, related tables from your db, there's no way to do it 
> with pg_dump within the one transactions (ie. maintaining integrity).  I 
> guess I'm in favour of -t -t but not -T depending on the complexity of 
> it.  I'll review the patch if you like.

One problem with this patch is that there's no way to dump multiple 
tables in different schemas.  Does this matter?  It's a bit 
non-orthogonal...

Chris


In response to

Responses

pgsql-hackers by date

Next:From: Zeugswetter Andreas SB SDDate: 2004-07-20 07:31:56
Subject: Re: localhost redux
Previous:From: Peter EisentrautDate: 2004-07-20 05:59:43
Subject: Re: pg_config

pgsql-patches by date

Next:From: Simon RiggsDate: 2004-07-20 09:04:29
Subject: Re: PITR COPY Failure (was Point in Time Recovery)
Previous:From: Peter EisentrautDate: 2004-07-20 05:59:43
Subject: Re: pg_config

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