Bug #805: pg_dump examines all tables even with -t "table_name" speficied - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #805: pg_dump examines all tables even with -t "table_name" speficied
Date
Msg-id 20021024153430.4BBA1475AD4@postgresql.org
Whole thread Raw
Responses Re: Bug #805: pg_dump examines all tables even with -t "table_name" speficied  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Vitaliy Fuks (vitaliyfuks@yahoo.com) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
pg_dump examines all tables even with -t "table_name" speficied

Long Description
Running pg_dump -t table_name -vv shows pg_dump examining every table in the database.  With many tables present (in
hundreds)this can make the process of dumping just one table take a considerable amount of time. 

With pg_dump -t specified it should go straight for the requested table and then figure what other dependent objects
needto be examined. 

Happens on pg_dump 7.2.3 under Linux (RedHat RPM) and i386 Solaris.

Are there some technical limitations forcing pg_dump to read everything?  If not it seems that the logic behind is just
notoptimal. 


Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #804: plpgsql not work on solaris
Next
From: Bruno Wolff III
Date:
Subject: set search_path documentation missing from development docs