Re: [HACKERS] pg_dump not in very good shape - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_dump not in very good shape
Date
Msg-id 24392.948053812@sss.pgh.pa.us
Whole thread Raw
In response to RE: [HACKERS] pg_dump not in very good shape  ("Ansley, Michael" <Michael.Ansley@intec.co.za>)
List pgsql-hackers
"Ansley, Michael" <Michael.Ansley@intec.co.za> writes:
>> So I'm leaning towards leaving the pg_dump code as-is and fixing the
>> limitation in pqexpbuffer.

> Yes, this is the correct solution.  What's the best way? To check the
> incoming string lengths for anything aproaching or greater than 1kB and
> slice it up from there?

I don't think we can do that short of writing a complete snprintf
emulation --- so we might as well just use snprintf.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Ansley, Michael"
Date:
Subject: RE: [HACKERS] pg_dump not in very good shape
Next
From: Mike Mascari
Date:
Subject: Re: [HACKERS] pg_dump not in very good shape