> On Jan 24, 2024, at 19:17, Sasmit Utkarsh wrote:
>
> Need your support on understanding advisory locks in Postgresql and what is
> the best practice to have advisory locks and unlocks to work properly when we
> have multiple process forked from single process?
Advisory locks are a shared
Hi Postgresql Team,
Need your support on understanding advisory locks in Postgresql and what is
the best practice to have advisory locks and unlocks to work properly when
we have multiple process forked from single process? is there any option
for setting the locktype or please share a sample prog
Michael Nolan writes:
> Including --with-openssl does include the crypto library, but if I
> don't do a 'make clean' before doing a make, I get errors when
> compiling postgresql. Apparently is it always a good idea to do make
> clean when reconfiguring postgresql.
Indeed. In theory, if you use
No, it wasn't there, because I hadn't included --with-openssl in the
configure. Looking at my history, I had done that once earlier but
dropped it for the reason noted below.
Including --with-openssl does include the crypto library, but if I
don't do a 'make clean' before doing a make, I get erro
Michael Nolan writes:
> Writing or debugging makefiles is something I haven't done much of,
> but as best I can figure out the problem is that the libcrypto.so file
> isn't being linked in, though this line in the Makefile in pgcrypto
> seems to say should be:
> SHLIB_LINK += $(filter -lcrypto -l
Sorry, I meant 'make check'. :sigh:
Writing or debugging makefiles is something I haven't done much of,
but as best I can figure out the problem is that the libcrypto.so file
isn't being linked in, though this line in the Makefile in pgcrypto
seems to say should be:
SHLIB_LINK += $(filter -lcrypto -lz, $(LIBS))
I'm guessing it is s
For this issue, I suggest you contact the packager, rather than the
software development community.
---
On Tue, Jan 23, 2024 at 04:55:27PM -0800, James Colannino wrote:
> A little while ago this month, this was reported:
>
On 1/24/24 02:48, Mickaël SALMON wrote:
Hello community,
I have a simple question about the duration of statements, which appear
in the logs when using :
log_min_duration_statement = 0
or
log_duration = on
Does this include client-time ? (i.e the time spent to send the data to
Hello community,
I have a simple question about the duration of statements, which appear in the
logs when using :
log_min_duration_statement = 0
or
log_duration = on
Does this include client-time ? (i.e the time spent to send the data to the
client). Or is it server-side only ?
Accord
>
> Le lun. 22 janv. 2024 à 08:29, James Pang a
> écrit :
>
>> [...] we used to turn on Oracle session trace(that will capture all
>> activities,
>>
> SQL statements, waiting, waiting time), to do living troubleshooting.
>>
> could you direct any similar tracing in Postgresql v13 , v14.
>>
>
On Tu
11 matches
Mail list logo
