public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: Durgamahesh Manne <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Regarding query optimisation (select for update)
Date: Tue, 15 Jul 2025 10:45:44 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAJCZko+fiU+=NSEGY7d7YMpFxg_jANpiO-LU6ur+yqRc_Ej6eQ@mail.gmail.com>
	<[email protected]>
	<CAJCZkoLJ6G9J3iK591o35UaKu3x7Kn96ma-u_yqGNgkrLjf6ag@mail.gmail.com>
	<[email protected]>

Laurenz Albe <[email protected]> writes:
> Text is easier to read than images...

Indeed.

> Anyway, this statement was done in under a millisecond.
> I wouldn't call that slow...

It looks to me like this EXPLAIN ANALYZE was done against a totally
empty table, so probably in a freshly-set-up dev environment.  That
is not going to be helpful in identifying your production problem.
Note the caveat at [1]:

    EXPLAIN results should not be extrapolated to situations much
    different from the one you are actually testing; for example,
    results on a toy-sized table cannot be assumed to apply to large
    tables.

			regards, tom lane

[1] https://www.postgresql.org/docs/current/using-explain.html#USING-EXPLAIN-CAVEATS

view thread (6+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Regarding query optimisation (select for update)
  In-Reply-To: <[email protected]>

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

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