Sorry, I missed that. Thanks again.
Now to put this all into effect.
John
On Mon, 25 Aug 2008 14:25:12 -0700, Joshua Drake wrote:
>On Mon, 25 Aug 2008 17:05:53 -0400
>"John T. Dow" <[EMAIL PROTECTED]> wrote:
>
>> Joshua
>>
>> Thank you very much for answering these various questions.
>>
>> I
On Mon, 25 Aug 2008 17:05:53 -0400
"John T. Dow" <[EMAIL PROTECTED]> wrote:
> Joshua
>
> Thank you very much for answering these various questions.
>
> I guess the compressed format is the best overall solution, except
> for roles. I find myself having a table with other information about
> user
Joshua
Thank you very much for answering these various questions.
I guess the compressed format is the best overall solution, except for roles. I
find myself having a table with other information about users (application
specific user type, etc) so perhaps the thing to do is record enough
info
On Mon, 25 Aug 2008 13:37:13 -0400
"John T. Dow" <[EMAIL PROTECTED]> wrote:
> Joshua
>
> The TOC feature sounds good, as does converting a single table to
> plain text.
>
> But I can't find documentation for the TOC feature under pg_dump or
> pg_restore. I'm looking in postgresql-8.2.1-US.pdf.
Joshua
The TOC feature sounds good, as does converting a single table to plain text.
But I can't find documentation for the TOC feature under pg_dump or pg_restore.
I'm looking in postgresql-8.2.1-US.pdf.
Neither could I see anything about converting a single table to a plain text
dump.
Also,
On Mon, 25 Aug 2008 10:21:54 -0400
"John T. Dow" <[EMAIL PROTECTED]> wrote:
> By "bad data", I mean a character that's not UTF8, such as hex 98.
>
> As far as I can tell, pg_dump is the tool to use. But it has
> serious drawbacks.
>
> If you dump in the custom format, the data is compressed (nic
Tom
My mistake in not realizing that 8.1 and later can dump large objects in the
plain text format. I guess when searching for answers to a problem, the posted
information doesn't always specify the version. So, sorry about that.
But the plain text format still has serious problems in that the
"John T. Dow" <[EMAIL PROTECTED]> writes:
> If you dump in plain text format, you can at least inspect the dumped
> data and fix it manually or with iconv. But the plain text
> format doesn't support large objects (again, not nice).
It does in 8.1 and later ...
> Also, neither of these methods ge
By "bad data", I mean a character that's not UTF8, such as hex 98.
As far as I can tell, pg_dump is the tool to use. But it has
serious drawbacks.
If you dump in the custom format, the data is compressed (nice) and
includes large objects (very nice). But, from my tests and the postings of
others,
