Re: TAP / recovery-test fs-level backups, psql enhancements etc

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: TAP / recovery-test fs-level backups, psql enhancements etc
Дата
Msg-id 20160301214633.GA373316@alvherre.pgsql
обсуждение исходный текст
Ответ на TAP / recovery-test fs-level backups, psql enhancements etc  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: TAP / recovery-test fs-level backups, psql enhancements etc  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
Craig Ringer wrote:
> Hi all
> 
> I've been working with the new TAP tests for recovery and have a number of
> enhancements I'd like to make to the tooling to make writing tests easier
> and nicer.

I think we should change the existing psql method to be what you propose
as psql_expert.  I don't see any advantage in keeping the old one.  Many
of the existing uses of psql should become what you call psql_check; but
we should probably call that psql_ok() instead, and also have a
psql_fails() for src/test/recovery/t/001_stream_rep.pl (and others to
come).

> +=item $node->backup_fs_hot(backup_name)
> +
> +Create a backup with a filesystem level copy in $node->backup_dir,
> +including transaction logs. Archiving must be enabled as pg_start_backup
> +and pg_stop_backup are used. This is not checked or enforced.

Perhaps "WAL archiving or streaming must be enabled ..."


I would rather have the patches be submitted with a reasonable
approximation at indentation rather than submit a separate indent patch.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pg_dump / copy bugs with "big lines" ?
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: 2016-03 Commitfest Manager