Re: In pageinspect, perform clean-up after testing gin-relatedfunctions

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: In pageinspect, perform clean-up after testing gin-relatedfunctions
Дата
Msg-id 20180711170244.i4l6y5wn52iuelgh@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: In pageinspect, perform clean-up after testing gin-related functions  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: In pageinspect, perform clean-up after testing gin-related functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2018-07-11 12:56:49 +0530, Amit Kapila wrote:
> On Wed, Jul 11, 2018 at 12:37 PM, Kuntal Ghosh
> <kuntalghosh.2007@gmail.com> wrote:
> > Hello all,
> >
> > In pageinspect/sql/gin.sql, we don't drop the table test1 at the end
> > of the test. IMHO, we should clean-up at the end of a test.
> >
> 
> Yeah, it is good practice to drop the objects at the end.  It is
> strange that original commit adfb81d9e1 has this at the end of the
> test, but a later commit 367b99bbb1 by Tom has removed the Drop
> statement.  AFAICS, this is just a silly mistake, but I might be
> missing something.  Tom, do you remember any reason for doing so?  If
> not, then I think we can revert back that change (aka commit Kuntal's
> patch).

We actually sometimes intentionally want to persist objects past the end
of the test. Allows to test pg_dump / pg_upgrade. Don't know whether
that's the case here, but it's worthwhile to note.

Greetings,

Andres Freund


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

Предыдущее
От: Marina Polyakova
Дата:
Сообщение: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: cursors with prepared statements