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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: In pageinspect, perform clean-up after testing gin-related functions
Date: 2018-07-11 17:02:44
Message-ID: 20180711170244.i4l6y5wn52iuelgh@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)2007(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-07-11 17:07:46 Re: cursors with prepared statements
Previous Message Marina Polyakova 2018-07-11 16:09:40 Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors