pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Tristan Partin <tristan@neon.tech>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Use COPY for populating all pgbench tables
Date: Thu, 13 Jul 2023 12:52:49 +0900
Message-ID: <ZK91ET3oYP2OMfDI@paquier.xyz> (raw)
In-Reply-To: <CU09K8PHEOIZ.I5NPQDPOQ1SO@gonk>
References: <CSTU5P82ONZ1.19XFUGHMXHBRY@c3po>
	<CTCG9VOM6GJ4.3NDBRQ7U4EP4Z@gonk>
	<CTCHWOCZ9X8Z.1PDXVDUXZ3D0P@gonk>
	<ZKzik5uamTwRWHsY@paquier.xyz>
	<CTZFAQT1PDPQ.30VM4JHGNU3J@gonk>
	<ZK5C26HdJlRJ/yOl@paquier.xyz>
	<CU09K8PHEOIZ.I5NPQDPOQ1SO@gonk>

On Wed, Jul 12, 2023 at 09:29:35AM -0500, Tristan Partin wrote:
> On Wed Jul 12, 2023 at 1:06 AM CDT, Michael Paquier wrote:
>> This would use the freeze option only on pgbench_accounts when no
>> partitioning is defined, but my point was a bit different.  We could
>> use the FREEZE option on the teller and branch tables as well, no?
>> Okay, the impact is limited compared to accounts in terms of amount of
>> data loaded, but perhaps some people like playing with large scaling
>> factors where this could show a benefit in the initial data loading.
> 
> Perhaps, should they all be keyed off the same option? Seemed like in
> your previous comment you wanted multiple options. Sorry for not reading
> your comment correctly.

I would have though that --partition should only apply to the
pgbench_accounts table, while FREEZE should apply where it is possible
to use it, aka all the COPY queries except when pgbench_accounts is a
partition.  Would you do something different, like not applying FREEZE
to pgbench_tellers and pgbench_branches as these have much less tuples
than pgbench_accounts?
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (31+ messages)  latest in thread

Message-ID: <ZK91ET3oYP2OMfDI@paquier.xyz>
Permalink:  ../ZK91ET3oYP2OMfDI@paquier.xyz/
Also on:    postgresql.org/message-id/ZK91ET3oYP2OMfDI@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: michael@paquier.xyz, tristan@neon.tech
  Subject: Re: Use COPY for populating all pgbench tables
  In-Reply-To: <ZK91ET3oYP2OMfDI@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox