On Thu, Dec 21, 2023 at 8:31 AM veem v wrote:
> Can someone please guide me, if any standard scripting is available for
> doing such read/write performance test? Or point me to any available docs?
>
>
> ...
Veem, first things first... "Top Posting" is when you reply at the top of
On Mon, Dec 25, 2023 at 1:47 PM Christophe Pettus wrote:
>
>
> > On Dec 25, 2023, at 10:44, Adrian Klaver
> wrote:
> > Functions with same name in different schemas would need to be dealt
> with.
>
> I think that's the primary use-case (at least, it would be for me), and I
> don't see a
On 12/26/23 18:02, Michael Nolan wrote:
I'm trying to install mysql_fdw_16 and it requires the mariadb-devel module.
From what I see the latest mysql_fdw version is REL-2_9_1, from here:
https://github.com/EnterpriseDB/mysql_fdw/releases/tag/REL-2_9_1
Are you getting it from some other
I'm trying to install mysql_fdw_16 and it requires the mariadb-devel module.
There is no mariadb-devel module for Almalinux 9. There is a
MariaDB-devel module, but when I install it, the install for
mysql_fdw_16 still tells me that there is no mariadb-devel module
available.
How do I work
On Wed, Dec 27, 2023 at 5:17 AM Clemens Eisserer wrote:
> > FWIW, since this crash is inside LLVM you could presumably dodge the bug
> > by setting "jit" to off.
>
> Thanks, this indeed solved the crash.
> Just to make sure this crash doesn't have anything to do with my
> setup/config (I'd
Sorry, wrong stack trace. Here is a correct one:
(gdb) bt
#0 0x7f9acca1bdf6 in do_futex_wait.constprop () from
/lib64/libpthread.so.0
#1 0x7f9acca1bee8 in __new_sem_wait_slow.constprop.0 () from
/lib64/libpthread.so.0
#2 0x007815a2 in PGSemaphoreLock ()
#3 0x007fca6c
On 12/26/23 12:51, Johnathan Tiamoh wrote:
Hello,
Please, I need help to fix this. Can't do anything in the database. This
error keeps popping up.
I have tried to do a pg_dump and the same error keeps coming up.
You need to provide answers to the questions posed here:
Hello,
Please, I need help to fix this. Can't do anything in the database. This
error keeps popping up.
I have tried to do a pg_dump and the same error keeps coming up.
Thank you
Johnathan Tiamoh
Dear PostgreSQL Community,
I am seeking guidance regarding a recurring issue we've encountered with
WAL segment removal during logical replication using pgoutput plugin. We
sporadically encounter an error indicating that a requested WAL segment has
already been removed. This issue arises
Hi Tom,
> FWIW, since this crash is inside LLVM you could presumably dodge the bug
> by setting "jit" to off.
Thanks, this indeed solved the crash.
Just to make sure this crash doesn't have anything to do with my
setup/config (I'd changed quite a few settings in postgresql.conf),
I gave it a try
Long story short, I tried setting REPLICA IDENTITY FULL on a table with a box
type and it made replication stall on the receiver because - as I found out
later - the predefined box type seems to lack a way to definitively determine
exact equality of coordinates.
I was tempted to post this as a
11 matches
Mail list logo
