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

Re: BUG #6660: losing schema name in pg_dump

From: Chaitany Kulkarni <shreeseva(dot)it(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6660: losing schema name in pg_dump
Date: 2012-05-23 17:42:06
Message-ID: CAAo-8uKBpAeZPHVp3VQxQ16rooAMXr2qAkJd+YhWczvaaZn9FA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Sorry for the late reply. But after comparing output results of pg_dump and
other tools in SQL format, I think it will helpful if an another switch is
provided in pg_dump to output data and definition of objects of only given
type.

e.g.
pg_dump --type views

It will export only views in given format for given other options such as
database, schema etc. Currently pg_dump supports to export the objects as
per the list but it is very difficult to list few hundred items there. So
it will be helpful when definitions and data of only certain types from a
schema are needed.

For SCM, I am looking for various options but SCM do not provide tools to
compare objects from two or more databases and database developers need
more options to manage database objects. Many times clients can change the
object definitions as per there needs and it becomes very hard to maintain
a version for each customer for a product. So looking to use Extension
mechanism or some thing else.

Thanks and regards,

C P Kulkarni


On Wed, May 23, 2012 at 11:11 PM, Chaitany Kulkarni
<shreeseva(dot)it(at)gmail(dot)com>wrote:

> On Tue, May 22, 2012 at 8:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Chaitany Kulkarni <shreeseva(dot)it(at)gmail(dot)com> writes:
>> > I didn't understand  when user have defined schema names explicitly in
>> > definition of the objects and most database developers insist on writing
>> > schema names explicitly, why pg_dump is not outputting it as it is.
>>
>> The short answer to that is that the internal representation of views
>> and other objects only stores object identities, not how they were named
>> in the input.  We don't store whitespace or layout choices either, and
>> there are various other ways that the output can vary from what you
>> typed.  So really, if you're intent on that, keeping the original source
>> file is the way to go.
>>
>>                        regards, tom lane
>>
>
>
>
>
> --
> Chaitanya P. Kulkarni
>
> Copyright. All rights are reserved for any object, text, ideas, images and
> any other things.
> -----------------------------------------------------------------------
> Keep your Environment clean and green.
> --------------------------xox----------------------------------------
>
>


-- 
Chaitanya P. Kulkarni

Copyright. All rights are reserved for any object, text, ideas, images and
any other things.
-----------------------------------------------------------------------
Keep your Environment clean and green.
--------------------------xox----------------------------------------

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2012-05-23 18:01:51
Subject: Re: BUG #6650: CPU system time utilization rising few times a day
Previous:From: Valentine GogichashviliDate: 2012-05-23 17:13:55
Subject: Re: BUG #6661: out-of-order XID insertion in KnownAssignedXids

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