Re: Snapshot synchronization, again...
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Snapshot synchronization, again... |
| Дата | |
| Msg-id | 1298303173-sup-6701@alvh.no-ip.org обсуждение |
| Ответ на | Re: Snapshot synchronization, again... (Joachim Wieland <joe@mcknight.de>) |
| Ответы |
Re: Snapshot synchronization, again...
|
| Список | 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 по дате отправления: