| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_dump problems against 7.0 |
| Date: | 2003-10-20 08:27:29 |
| Message-ID: | 3F939C71.6090809@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I noticed that the function to get max builtin OID for 7.0 does this:
template1=> SELECT oid from pg_database where datname = 'template1';
oid
-------
17216
(1 row)
However, that is incorrect:
template1=> select oid,relname from pg_class where oid > 17216;
oid | relname
-------+------------
17408 | pg_indexes
17280 | pg_user
17312 | pg_rules
17344 | pg_views
17376 | pg_tables
(5 rows)
Which results in all the system views being dumped. Attached is a
patch. Please tell me if it's OK.
Chris
| Attachment | Content-Type | Size |
|---|---|---|
| dumpviews.txt | text/plain | 710 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2003-10-20 08:42:16 | Re: Debian bug report about multibyte in 7.3.3 |
| Previous Message | Fabien DAUMEN | 2003-10-20 08:12:28 | Can't not load libpq.so.3 |