From: spiral <spiral@spiral.sh>
To: Justin Pryzby <pryzby@telsasoft.com>
To: pgsql-performance@postgresql.org
Subject: Re: Advice on best way to store a large amount of data in postgresql
Date: Tue, 10 Jan 2023 04:25:38 -0500
Message-ID: <20230110042538.44cad73b@xps> (raw)
In-Reply-To: <20230109175647.GB9837@telsasoft.com>
References: <20230108070201.39b19d30@xps>
<20230109175647.GB9837@telsasoft.com>
(re-sending this because I forgot to use "reply all". Sorry!)
On Mon, 9 Jan 2023 11:56:47 -0600
Justin Pryzby <pryzby@telsasoft.com> wrote:
> Are you using the extended query protocol with "bind" parameters, or
> are they escaped and substituted by the client library ?
Our client library uses parameters, yes. "$1" is passed literally to
postgres.
> can you arrange your partitioning such that the things to be dropped
> are all in one partition, to handle in bulk ?
Unfortunately, no. Deletes are all generated from user actions - if a
user deletes one message, we need to delete one single row from our
database.
> [...] one of the main reasons for using partitioning
> How many "partitions" do you have (actually, timescale uses
> inheritance) ?
We have ~1600 timescaledb chunks. We could increase the chunk count. We
could also stop using partitions/chunks if it would improve things. I'm
currently setting up a test database without partitioning to see what
the performance would look like.
spiral
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-performance@postgresql.org
Cc: spiral@spiral.sh, pryzby@telsasoft.com
Subject: Re: Advice on best way to store a large amount of data in postgresql
In-Reply-To: <20230110042538.44cad73b@xps>
* 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