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

Re: pg_dump --no-tablespaces patch

From: "Gavin M(dot) Roy" <gmr(at)myyearbook(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_dump --no-tablespaces patch
Date: 2007-08-30 15:39:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
I wanted to push to see if I made a version of this patch against CVS
head if we could see it included in 8.3.

It's of clear value for people who use pg_dump and tablespaces.  HOT
and tsearch development still continues and implementations of each
feature are still being discussed/debated as of this morning.  It
seems to me that 8.3 code base is not static and we're not at the bug
cleanup phase of nearing release.

This patch is minor and makes admin, backup and recovery much easier
for people who use the tablespace feature and elect not to use
pg_dumpall.  I think waiting for 8.4 at this point is a bit silly,
given the scope of code and impact of the patch.


On 7/17/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> This has been saved for the 8.4 release:
> ---------------------------------------------------------------------------
> Gavin M. Roy wrote:
> > This is the patch I proposed on hackers to make pg_dump optionally ignore
> > tablespaces.  The patch is against 8.2.4.  If I should be applying it to CVS
> > head or what not, please let me know (along with any thoughts, concerns or
> > issues).
> >
> > Gavin
> [ Attachment, skipping... ]
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: Don't 'kill -9' the postmaster
> --
>   Bruce Momjian  <bruce(at)momjian(dot)us>
>   EnterpriseDB                     
>   + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-08-30 15:56:41
Subject: Re: pg_dump --no-tablespaces patch
Previous:From: Tom LaneDate: 2007-08-30 15:16:39
Subject: Re: HOT patch - version 14

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