Re: Snapshot synchronization, again... - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Snapshot synchronization, again...
Date
Msg-id 1298303173-sup-6701@alvh.no-ip.org
Whole thread Raw
In response to Re: Snapshot synchronization, again...  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Snapshot synchronization, again...  (Joachim Wieland <joe@mcknight.de>)
List pgsql-hackers
A couple more questions:

What's the reason for this restriction?if (databaseId != MyDatabaseId)    ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE),        errmsg("cannot import snapshot from a different database")));
 

Why are we using bytea as the output format instead of text?  The output
is just plain text anyway, as can be seen by setting bytea_output to
'escape'.  Perhaps there would be a value to using bytea if we were to
pglz_compress the result, but would there be a point in doing so?
Normally exported info should be short enough that it would cause more
overhead than it would save anyway.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL FDW update
Next
From: Andrew Dunstan
Date:
Subject: Re: FDW API: don't like the EXPLAIN mechanism