Re: SerializeParamList vs machines with strict alignment

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, hlinnaka <hlinnaka(at)iki(dot)fi>
Subject: Re: SerializeParamList vs machines with strict alignment
Date: 2018-10-02 04:26:37
Message-ID: CAA4eK1KknpFLC1jEAP7n_fp65tTSd0nWnEQ65X=w=hCT8vB2ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 2, 2018 at 9:38 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> > On Tue, Oct 2, 2018 at 9:22 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> (I think we could drop the savepoint
> >> too, no?)
>
> > One advantage of keeping the savepoint is that we don't need to
> > explicitly drop the objects which we have created temporarily for this
> > test.
>
> They'll go away anyway at the end of the transaction that the whole
> script is wrapped in.

That's right, will remove savepoint.

> (But it might be worth choosing slightly less
> generic object names, to avoid a conflict against other sub-tests
> later in that script.)
>

The function name and statement name seems okay to me. How about
changing the table name to fooarr or arrtest?

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-10-02 04:31:03 Re: [HACKERS] Secondary index access optimizations
Previous Message Masahiko Sawada 2018-10-02 04:18:01 Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru