Hi Alexander,
Thanks for collating this list.
I'll try to add as much as I know, in hopes that it helps.
On Sun, 22 Dec 2024 at 16:30, Alexander Lakhin wrote:
> I'd like to bring your attention to multiple buildfarm failures, which
> occurred this month, on master only, caused by "could not ope
Hello hackers,
I'd like to bring your attention to multiple buildfarm failures, which
occurred this month, on master only, caused by "could not open shared
memory segment ...: No such file or directory" errors.
First such errors were produced on 2024-12-16 by:
leafhopper
Amazon Linux 2023 | gcc
hi.
I did some cosmetic changes:
expand commit message.
remove unnecessary parentheses around errcode, per
https://git.postgresql.org/cgit/postgresql.git/commit/?id=e3a87b4991cc2d00b7a3082abb54c5f12baedfd1
change two errorcode from ERRCODE_UNDEFINED_FUNCTION
to ERRCODE_FEATURE_NOT_SUPPORTED
in fun
On 12/12/2024 22:26, Heikki Linnakangas wrote:
On 12/12/2024 21:57, Andres Freund wrote:
Perhaps we should have some assertions ensuring TransactionXmin has a
valid
value in some places?
+1, wouldn't hurt.
I didn't, after all, as I couldn't find a good place where to put that.
There are a
On 10/29/24 8:55 PM, Andreas Karlsson wrote:
I especially dislike the static variable in our patch. And as far as I
understand it you can avoid the static by changing the lexer to use the
push parser so it can emit multiple terminal tokens from one parsed
token, but I have not looked into push
Hi,
Our runtime stats system is great, but it only keeps a snapshot of
cumulative stats / snapshot. And while that works for user workloads, it
may not be quite sufficient when analyzing maintenance operations like
vacuum/checkpoint, etc.
For those operations it's useful to have information about
> On Dec 20, 2024, at 4:45 PM, Tom Lane wrote:
>
> "David G. Johnston" writes:
>> On Friday, December 20, 2024, Tom Lane wrote:
>>> * "Listen to all but X" seems like a reasonable desire.
>
>> This I concur with, and would add: let me name my channels
>> accounting.payables, accounting.recei
On Tue, Dec 17, 2024 at 5:51 PM Melanie Plageman
wrote:
>
> Thanks for taking a look!
>
> I've rebased and attached an updated v3 which also addresses review feedback.
>
> On Sun, Dec 15, 2024 at 1:05 AM Robert Treat wrote:
> > On Fri, Dec 13, 2024 at 5:53 PM Melanie Plageman
> > wrote:
>
> So,
On 2024-12-20 Fr 5:21 AM, Corey Huinker wrote:
I recently had occasion to use the pg_parse_json() function for
creating input functions for pg_ndistinct and pg_dependencies.
While it is obvious now that I should have been parsing with
need_escapes=true, it wasn't obvious from the outset, and
Hi Ashutosh,
On Fri, Dec 6, 2024 at 12:34 AM Ashutosh Bapat
wrote:
>
> Sorry, I forgot to attach patches. PFA the patches.
>
> On Thu, Dec 5, 2024 at 4:38 PM Ashutosh Bapat
> wrote:
> >
> > On Fri, Nov 22, 2024 at 7:29 PM Ashutosh Bapat
> > wrote:
> > >
> > > On Tue, Nov 19, 2024 at 10:08 PM Vi
On 20.12.24 16:35, Tom Lane wrote:
Julien Rouhaud writes:
On Fri, Dec 20, 2024 at 11:23 PM Tom Lane wrote:
Could we get that animal updated to
some newer OS version?
There is already adder animal that is running debian sid on i386. The
only remaining interest in lapwing is to have older v
>
>
> I like the description "STATISTICS DATA" because it differentiates from
>
You have Tomas to thank for that:
https://www.postgresql.org/message-id/bf724b21-914a-4497-84e3-49944f9776f6%40enterprisedb.com
the extended stats definitions. It might be worth differentiating
> between "RELATION ST
On Thu, Dec 19, 2024, at 14:40, Andrew Dunstan wrote:
> We seem to have got seriously into the weeds, here. I'd be sorry to see
> this dropped. After all, it's not something new, and while we have a
> sort of workaround for "one json doc per line" it's far from obvious,
> and except in a few blo
13 matches
Mail list logo
