Re: pg_restore (libpq? parser?) bug in 8 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_restore (libpq? parser?) bug in 8
Date
Msg-id 23283.1092278535@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_restore (libpq? parser?) bug in 8  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_restore (libpq? parser?) bug in 8  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> At 12:15 PM 12/08/2004, Tom Lane wrote:
>> Why exactly does pg_restore need to parse the SQL anyway?

> It just looks for complete statements. From memory it relates to the 
> possibility that TOC entries can have more than one statement, or it may 
> relate to handling COPY statements. I think it has to look for 
> PQresultStatus(...) == PGRES_COPY_IN for each statement it executes, so it 
> needs to pass statements one at a time.

Hm.  But we could assume that a COPY will be all by itself in a TOC
entry, couldn't we?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: dollar-quoting in psql and in general
Next
From: Tom Lane
Date:
Subject: Re: will PITR in 8.0 be usable for "hot spare"/"log shipping" type