| From: | pgsql-bugs(at)postgresql(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Bug #805: pg_dump examines all tables even with -t "table_name" speficied |
| Date: | 2002-10-24 15:34:30 |
| Message-ID: | 20021024153430.4BBA1475AD4@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Vitaliy Fuks (vitaliyfuks(at)yahoo(dot)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 need to 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 not optimal.
Sample Code
No file was uploaded with this report
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2002-10-24 15:56:15 | set search_path documentation missing from development docs |
| Previous Message | Tom Lane | 2002-10-24 14:31:12 | Re: Bug #804: plpgsql not work on solaris |