Re: register/unregister standby Re: Synchronous replication
| От | Itagaki Takahiro |
|---|---|
| Тема | Re: register/unregister standby Re: Synchronous replication |
| Дата | |
| Msg-id | AANLkTim0=-8oU2PSUeEvGiWZJtYcuBkG08Y=7HS6v6dY@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: register/unregister standby Re: Synchronous replication (Dimitri Fontaine <dfontaine@hi-media.com>) |
| Список | pgsql-hackers |
On Thu, Sep 2, 2010 at 7:54 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote:
>> One issue of the base backup function is that the operation will
>> be a long transaction. So, non-transactional special commands,
>> as like as VACUUM, would be better in terms of performance.
>> For example, CREATE or ALTER REPLICATION.
>
> Well, you still need to stream the data to the client in a format it
> will understand.
True, but using libpq connection might be not the most important thing.
The most simplest proof-of-concept might be system("rsync") in the function ;-)
> Would that be the plan of your command proposal?
What I meant was function-based maintenance does not work well in some
cases. I heard before pg_start_backup( no-fast-checkpoint ) caused table
bloating problem because it was a long transaction for 20+ minutes.
The backup function would have the similar issue.
--
Itagaki Takahiro
В списке pgsql-hackers по дате отправления: