On Fri, 11 Aug 2023 at 13:54, Ron wrote:
> Wouldn't IO contention make for additive timings instead of exponential?
No, not necessarily. Imagine one query running that's doing a
parameterised nested loop join resulting in the index on the inner
side being descended several, say, million times. L
Wouldn't IO contention make for additive timings instead of exponential?
On 8/10/23 20:41, Adam Scott wrote:
I think your concern is that 20 min + 30 min does not equal 3 hours.
It might be natural to think the contention would, at max, be 50 min x 2
(1 hr 40 min).
So what's going on?
It se
I think your concern is that 20 min + 30 min does not equal 3 hours.
It might be natural to think the contention would, at max, be 50 min x 2 (1
hr 40 min).
So what's going on?
It seems disk I/O is a primary suspect since you hint for an iostat
replacement inside of Postgres.
If it is due to d
On 8/10/23 16:36, Marc Millas wrote:
Hi,
I have a 15 TB db on postgres 14 (soon 15).
shared buffers is 32 GB.
Does the system have 128GB AM?
It's a db with max 15 users and often less, and currently 1 or 2.
the biggest table have 133 partitions of 150M to 200M+ rows each.
lots of request ac
Hi,
I have a 15 TB db on postgres 14 (soon 15).
shared buffers is 32 GB.
It's a db with max 15 users and often less, and currently 1 or 2.
the biggest table have 133 partitions of 150M to 200M+ rows each.
lots of request access explicitly one of those.
When I, alone, run a query "reading" 15M bu
On Wednesday, August 9, 2023, Erik Nelson wrote:
> I have a lab with a database that I would like to use as a "multi-tenant"
> database, in that I would like to create a database for each of the
> applications that I'm running and segregate access so that user foo and
> user bar cannot see anythi
On 8/9/23 01:14, Dürr Software wrote:
Dear list,
i have a strange problem when migrating a DB from version 9.3.4 to 15.3:
An index which seems perfect for the query and is used in 9.3.4 as
expected is not used in 15.3.
Did you run ANALYZE on the 15.3 database after the migration?
--
Adrian
I have a lab with a database that I would like to use as a "multi-tenant"
database, in that I would like to create a database for each of the
applications that I'm running and segregate access so that user foo and
user bar cannot see anything about their neighbors. I'm somewhat surprised
to discove
Dear list,
i have a strange problem when migrating a DB from version 9.3.4 to 15.3:
An index which seems perfect for the query and is used in 9.3.4 as
expected is not used in 15.3.
I just wonder, whether the bug is on my side or on PgSQL's..
The details:
