Re: [HACKERS] pgbench: Skipping the creating primary keys afterinitialization - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] pgbench: Skipping the creating primary keys afterinitialization
Date
Msg-id alpine.DEB.2.20.1711131949120.18461@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench: Skipping the creating primary keys after initialization  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] pgbench: Skipping the creating primary keys after initialization
List pgsql-hackers
>> Note that if "c" is freed by "d" (drop), then it may be worth considering
>> that "t" (table) could be replaced by "c" (create).
>
> I thought about that, but the argument that 'c' might mean different 
> sorts of create steps (e.g. create index) seemed reasonable. I think 
> we're best off leaving it as 't' in case of future expansion.

Ok. Fine with me.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] pg audit requirements
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Add hash partitioning.