Re: Bug #805: pg_dump examines all tables even with -t "table_name" speficied

From: Vitaliy Fuks <vitaliyfuks(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #805: pg_dump examines all tables even with -t "table_name" speficied
Date: 2002-10-29 19:13:15
Message-ID: 20021029191315.4807.qmail@web13508.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

Could there potentially be an option in addition to -t "table_name", to
either:

a) Examine all relationships and dump all dependant objects
b) Dump only table named "table_name"

One can argue that when asking for "a" table one really only wants that
table information, and nothing else. Some people of course can argue
that just a table by itself may not be usable by itself in some
situations - so that's why the option described above could cater both
situations.

I wish I could just give you a patch but there are probably people who
know pg_dump internals who could produce such patch in 10x less amount
of time.

--Vitaliy

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> pgsql-bugs(at)postgresql(dot)org writes:
> > pg_dump examines all tables even with -t "table_name" speficied
>
> 7.3 is a little better. It's not that easy to determine in advance
> what
> information is needed, though; consider inheritance for example.
>
> regards, tom lane

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Shibashish 2002-10-29 21:19:16 PostgreSQL Installation on SCO
Previous Message Bruce Momjian 2002-10-29 18:54:22 Re: Bug #807: Sequence currupted on recovery after kill -9