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

Re: Problem with pg_dump -n schemaname

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zoltan Boszormenyi <zb(at)cybertec(dot)at>, List pgsql-patches <pgsql-patches(at)postgresql(dot)org>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: Re: Problem with pg_dump -n schemaname
Date: 2007-11-24 20:15:37
Message-ID: 200711242015.lAOKFbD14034@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> The fact that schema ss might not exist is one of the scenarios that
> we need to qualify the primary name in the DROP to protect against.
> It's possible say that "complex" would get mis-resolved as some other
> type "complex" in some other schema, but it doesn't matter since the
> qualified function name will surely not match anything else.
> 
> What I think we ought to do is just reset currSchema once, after the
> DROP phase is completed, whether or not any schemas were dropped.
> This will be considerably more bulletproof in partial-restore
> situations.
> 
> Will go fix.

OK.  I did consider that option but was unsure of the ramifications.
The problem is definitely subtle.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-11-24 20:19:21
Subject: Re: backup_label and server start
Previous:From: Tom LaneDate: 2007-11-24 20:07:44
Subject: Re: Problem with pg_dump -n schemaname

pgsql-patches by date

Next:From: Tom LaneDate: 2007-11-25 01:40:45
Subject: Proposed patch to adjust UNION/CASE/etc type resolution rules
Previous:From: Tom LaneDate: 2007-11-24 20:07:44
Subject: Re: Problem with pg_dump -n schemaname

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