From: | Tomas Vondra <tomas(at)vondra(dot)me> |
---|---|
To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Extension disappearing act |
Date: | 2025-06-20 09:11:47 |
Message-ID: | 3978528f-d76c-4a10-bf3e-7f599770709a@vondra.me |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/20/25 09:35, Dominique Devienne wrote:
> On Thu, Jun 19, 2025 at 6:35 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>>
>> On Thu, 2025-06-19 at 15:09 +0200, Dominique Devienne wrote:
>>> Hi. Little mystery we don't understand. v17.
>>> We're stumped for now.
>>
>> So are we. Why do you keep us guessing instead of posting a reproducer?
>
> Hi. Simply because there's too much proprietary stuff, I'm afraid.
> And it's likely some stupid mistakes on our part anyway. That I can't see...
> Still, the fact I see nothing extension-related in the libpq trace is
> intriguing, isn't it?
>
PQtrace logs client-server communication. I would not expect it to say
anything about actions that happen on the server, like for example
automatically dropping objects in a schema, after the schema is dropped.
I think the best way to move this forward is sharing a reproducer. If
you have too much proprietary stuff, you'll have to remove those bits,
or rather replace them with something you can share.
In fact, a reproducer is meant to be "minimal" - the smallest example
causing the issue. So creating reproducers generally means simplifying
the example as much as possible anyway. And I wouldn't be surprised if
in the process of doing that you find the answer yourself.
regards
--
Tomas Vondra
From | Date | Subject | |
---|---|---|---|
Next Message | sivapostgres@yahoo.com | 2025-06-20 11:08:41 | Re: Retrieving current date |
Previous Message | Dominique Devienne | 2025-06-20 07:35:19 | Re: Extension disappearing act |