Re: pg_dump tries to do too much per query - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_dump tries to do too much per query
Date
Msg-id 3.0.5.32.20000918152538.02f996b0@mail.rhyme.com.au
Whole thread Raw
In response to pg_dump tries to do too much per query  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 16:29 17/09/00 -0400, Tom Lane wrote:
>As somebody pointed out a few days ago, pg_dump silently loses tables
>whose owners can't be identified.  

This is now fixed in CVS. The owner of all objects are now retrieved by
using column select expressions.

If you can recall where it was, I'd be interested in seeing the report
since I have no recollection of it, and I try to keep abreast of pg_dump
issues...



----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: pg_dump tries to do too much per query
Next
From: Tom Lane
Date:
Subject: Re: Notice and share memory corruption