Thx,
Created an issue ( https://github.com/pgdg-packaging/pgdg-rpms/issues/67 )
for the debuginfo repository; time correlation is there as you mentioned.
Kind regards Ales Zeleny
út 5. 8. 2025 v 17:04 odesílatel Adrian Klaver
napsal:
> On 8/5/25 01:05, Aleš Zelený wrote:
> > The pgdg16-debugin
On 8/5/25 01:05, Aleš Zelený wrote:
The pgdg16-debuginfo repository suffers from another issue (yesterday it
worked):
You should be bringing this up here:
https://github.com/pgdg-packaging/pgdg-rpms/issues/
Failed to download metadata for repo 'pgdg16-debuginfo': repomd.xml GPG
signature v
On Tue, Aug 5, 2025 at 3:20 PM Álvaro Herrera wrote:
> On 2025-Aug-05, Dominique Devienne wrote:
> Yeah, I think that makes sense. Feel free to propose a patch.
OK, fair enough. If I ever do (fat chances), I'd add another opt-in flag
to make the trace machine readable (see my older thread about
On 2025-Aug-05, Dominique Devienne wrote:
> Hi. I'm using PQtrace for client-side tracing with PQtrace,
> which I thought was showing protocol messages in details.
>
> But turns out that RAISE notices from PL/pgSQL are not there.
Hmm, don't they show up as NOTICE messages? I think they should.
Hi. I'm using PQtrace for client-side tracing with PQtrace,
which I thought was showing protocol messages in details.
But turns out that RAISE notices from PL/pgSQL are not there.
And to think about it, I wonder whether NOTIFY messages are there too.
Are these oversights?
Any chance this could
The pgdg16-debuginfo repository suffers from another issue (yesterday it
worked):
Failed to download metadata for repo 'pgdg16-debuginfo': repomd.xml GPG
signature verification error: Bad GPG signature
Kind regards Ales Zeleny
po 4. 8. 2025 v 17:20 odesílatel Aleš Zelený napsal:
> Probably du
