Re: Updated backup APIs for non-exclusive backups
| От | Amit Kapila |
|---|---|
| Тема | Re: Updated backup APIs for non-exclusive backups |
| Дата | |
| Msg-id | CAA4eK1JjbY1pZmCyX_1OeCH4jpE=7UPoZw9QQ3bOYOY=nvhMhw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Updated backup APIs for non-exclusive backups (Magnus Hagander <magnus@hagander.net>) |
| Ответы |
Re: Updated backup APIs for non-exclusive backups
|
| Список | pgsql-hackers |
On Wed, Mar 2, 2016 at 6:49 PM, Marco Nenciarini <marco.nenciarini@2ndquadrant.it> wrote:I've attached an updated patch, which is rebased on current master and includes the oid fix.
+ <entry>Finish performing exclusive on-line backup (restricted to superusers or replication roles)</entry>
+ </row>
+ <row>
+ <entry>
+ <literal><function>pg_stop_backup(<parameter>exclusive</> <type>boolean</>)</function></literal>
+ </entry>
+ <entry><type>setof record</type></entry>
+ <entry>Finish performing exclusive or non-exclusive on-line backup (restricted to superusers or replication roles)</entry>
<para>
<function>pg_start_backup</> accepts an
arbitrary user-defined label for the backup. (Typically this would be
the name under which the backup dump file will be stored.) The function
writes a backup label file (<filename>backup_label</>) and, if there
are any links in the <filename>pg_tblspc/</> directory, a tablespace map
file (<filename>tablespace_map</>) into the database cluster's data
directory, performs a checkpoint, and then returns the backup's starting
transaction log location as text. The user can ignore this result value,
but it is provided in case it is useful.
CREATE OR REPLACE FUNCTION
- pg_start_backup(label text, fast boolean DEFAULT false)
+ pg_start_backup(label text, fast boolean DEFAULT false, exclusive boolean DEFAULT true)
RETURNS pg_lsn STRICT VOLATILE LANGUAGE internal AS 'pg_start_backup';
В списке pgsql-hackers по дате отправления: