On Mon, Jan 22, 2024 at 11:43 PM Heikki Linnakangas wrote:
> On 22/01/2024 21:58, Vladimir Churyukin wrote:
> > A question about protocol design - would it be possible to extend the
> > protocol, so it can handle multiple startup / authentication messages
> > over a single
On Mon, Jan 22, 2024 at 11:43 PM Heikki Linnakangas wrote:
> On 22/01/2024 21:58, Vladimir Churyukin wrote:
> > A question about protocol design - would it be possible to extend the
> > protocol, so it can handle multiple startup / authentication messages
> > over a single
utilization on clients (on the db side too). A lot
of other RDBMSes don't have this limitation.
thank you,
-Vladimir Churyukin
On Sat, Nov 11, 2023 at 7:49 AM Tom Lane wrote:
> Vladimir Churyukin writes:
> > Why not have an option to return EXPLAIN results as a NoticeResponse
> > instead? That would make its usage more convenient.
>
> That seems quite useless to me, and likely actually counterpro
Thank you, that answers the first part of my question.
On Sat, Nov 11, 2023 at 2:43 AM Sergei Kornilov wrote:
> Hello
>
> auto_explain.log_level is available since postgresql 12.
>
> postgres=# load 'auto_explain';
> LOAD
> postgres=# set auto_explain.log_min_duration to 0;
> SET
> postgres=# se
o check if there
are any objections in general.
Thank you,
-Vladimir Churyukin.
On Thu, Jun 15, 2023 at 12:32 AM Konstantin Knizhnik
wrote:
>
>
> On 15.06.2023 4:37 AM, Vladimir Churyukin wrote:
> > Ok, got it, thanks.
> > Is there any alternative approach to measuring the performance as if
> > the cache was empty?
> > The goal is basically
It could be cheaper, if the testing is done for many SELECT queries
sequentially - you need to flush dirty buffers just once pretty much.
-Vladimir Churyukin
On Wed, Jun 14, 2023 at 7:43 PM Tom Lane wrote:
> Thomas Munro writes:
> > There are two levels of cache. If you're on
a though
(if a large prewarm operation really evicts all the previously stored data
reliably).
It's a bit hacky, but thanks, I think it's possible to make this work with
some effort.
It will require exclusive access just for that testing, which is not ideal
but may work for us.
-Vladim
all? Is there a
different way to simulate something like that?
-Vladimir Churyukin
On Wed, Jun 14, 2023 at 6:22 PM Tom Lane wrote:
> Vladimir Churyukin writes:
> > There is often a need to test particular queries executed in the
> worst-case
> > scenario, i.e. right after a server res
To be clear, I'm talking about bypassing shared buffers for reading data /
indexes only, not about disabling it completely (which I guess is
impossible anyway).
-Vladimir Churyukin
On Wed, Jun 14, 2023 at 5:57 PM Vladimir Churyukin
wrote:
> Hello,
>
> There is often a need to t
ciple?
Thanks,
-Vladimir Churyukin
On Wed, Feb 22, 2023, 12:40 PM Andres Freund wrote:
> Hi,
>
> On 2023-02-11 12:47:04 -0800, Vladimir Churyukin wrote:
> > That is a good idea for simple cases, I'm just curious how it would look
> > like for more complex cases (you can have all kinds of express
uld be good, no? Just my 2 cents.
-Vladimir Churyukin
On Sat, Feb 11, 2023 at 11:24 AM Andres Freund wrote:
> Hi,
>
> A common annoyance when writing ad-hoc analytics queries is column naming
> once
> aggregates are used.
>
> Useful column names:
> SELECT reads, writes FROM pg
logic doesn't
slow down something else dramatically?
I see some EXPLAIN output checks in regression tests (not that many
though), so I'm curious how regressions in planning are currently tested.
Not the simple ones, when you have a small input and predictable
plan/output, but something that can happen with more or less real data
distribution on medium / large datasets.
-Vladimir Churyukin
On Tue, Jan 3, 2023 at 7:41 PM David Rowley wrote:
> On Wed, 4 Jan 2023 at 16:15, Vladimir Churyukin
> wrote:
> > As an end user that spends a lot of time optimizing pretty complicated
> queries, I'd say that something like this could be useful.
>
> I think we really
As an end user that spends a lot of time optimizing pretty complicated
queries, I'd say that something like this could be useful.
Right now the optimizer is mostly a black box. Why it chooses one plan or
the other, it's a mystery. I have some general ideas about that,
and I can even read and someti
17 matches
Mail list logo
