Christopher Kings-Lynne wrote:
> > Oh, if we do that, do we disallow connecting to older servers?
>
> Not at all, since the logic would be like this:
>
> if we have new copy functions
>and we have protocol version function
> and protocol version >= 3
>then use new copy functions
Christopher Kings-Lynne wrote:
> > We have been telling people to use newer pg_dump's on older servers, but
> > we only support reloading into the current PostgreSQL version, so I see
> > no reason not to updated it to the current syntax.
> >
> > We added the new syntax in 7.3.
> >
> > Added to T
Oh, if we do that, do we disallow connecting to older servers?
Not at all, since the logic would be like this:
if we have new copy functions
and we have protocol version function
and protocol version >= 3
then use new copy functions
else
use old copy functions
That would be even simpl
We have been telling people to use newer pg_dump's on older servers, but
we only support reloading into the current PostgreSQL version, so I see
no reason not to updated it to the current syntax.
We added the new syntax in 7.3.
Added to TODO:
o Update pg_dump to use the newer COPY syntax
I think y
Christopher Kings-Lynne wrote:
> Should psql and pg_dump be upgraded to use the new v3 protocol copy
> functions if they are available, as they are currently using the
> deprecated API.
We have been telling people to use newer pg_dump's on older servers, but
we only support reloading into the cu
Should psql and pg_dump be upgraded to use the new v3 protocol copy
functions if they are available, as they are currently using the
deprecated API.
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
