Hello,
I am able to start postgresql because of the below error. Please is there
any help
[image: User]
You
FATAL: xlog flush request 4392/164662F8 is not satisfied --- flushed only
to 4392/F58
[image: User]YouFATAL: xlog flush request 4392/164662F8 is not satisfied
--- flushed only to 43
On Sat, Dec 23, 2023 at 8:36 AM Phillip Diffley wrote:
>
> Thank you for all the suggestions! I ended up using pgcrypto's
> pg_random_bytes() to build the random int. I haven't fully tested the
> function yet, but it looks like this works.
>
> CREATE EXTENSION IF NOT EXISTS pgcrypto;
> CREATE OR R
Thank you for all the suggestions! I ended up using pgcrypto's
pg_random_bytes() to build the random int. I haven't fully tested the
function yet, but it looks like this works.
CREATE EXTENSION IF NOT EXISTS pgcrypto;
CREATE OR REPLACE FUNCTION gen_random_int() RETURNS INT8 AS $$
DECLARE
bytes byt
On 12/22/23 15:09, Wilma Wantren wrote:
Thank you for your response!
No, this does not help me. I will try to explain better what I mean. Our
customers use our program with a Postgres database, user and schema, which have
the same name. The customer chooses the name. Let's say one customer call
Thank you for your response!
No, this does not help me. I will try to explain better what I mean. Our
customers use our program with a Postgres database, user and schema, which have
the same name. The customer chooses the name. Let's say one customer calls the
database, user and schema 'my_thin
"Peter J. Holzer" writes:
> On 2023-12-22 10:31:14 -0500, Tom Lane wrote:
>> Binaek Sarkar writes:
>>> Interestingly, the *build completes successfully when the .a file is
>>> smaller* (around 100 MB).
>> Pure luck I suspect.
> I seem to remember a 256MB limit for position independent code on x
On 2023-12-22 10:31:14 -0500, Tom Lane wrote:
> Binaek Sarkar writes:
> > The issue arises with a Go module that is compiled into a .a archive file
> > using -buildmode=c-archive, leading to a *file size of approximately 393
> > MB*.
[...]
> > Interestingly, the *build completes successfully when
Binaek Sarkar writes:
> The issue arises with a Go module that is compiled into a .a archive file
> using -buildmode=c-archive, leading to a *file size of approximately 393 MB*.
I am not sure exactly what "-buildmode=c-archive" does, but it doesn't
sound like it is doing what you need. You need
Hello Laurenz,
Thank you very much for your reply.
On Fri, Dec 22, 2023 at 7:10 AM Laurenz Albe
wrote:
> On Thu, 2023-12-21 at 18:53 -0500, Johnathan Tiamoh wrote:
> > Please I wish to find out what you do after running pg_walreset.
>
> You mean pg_resetwal.
>
> > I made a mistake and deleted m
As I mentioned your scenario looks generic one, but I don't have any sample
scripts/docs to share, sorry for that. Other people may suggest any sample
scripts etc if any. or you may post it on performance group, if someone has
done similar stuff in the past.
But as per me, the performance test sc
On Thu, 2023-12-21 at 18:53 -0500, Johnathan Tiamoh wrote:
> Please I wish to find out what you do after running pg_walreset.
You mean pg_resetwal.
> I made a mistake and deleted my data directory with all its content.
> I then restore with 1 day old backups, after that i could start
> unless i d
I am new to PostgreSQL extension development and am currently working on
the *steampipe-postgres-fdw* project.
This is a *Foreign Data Wrapper (FDW) written in Go*, and while I have
successfully built it on Darwin systems, I am facing challenges when
building on Linux, particularly with *pgxs.mk <
We are using logical replication in a quite busy environment. On the
publisher side temporary tables are created and dropped all the time (due
to some Zend Entity Framework extension "optimisation"), thus bloating
heavily the system catalogs (among others).
At some point all our logical replicatio
13 matches
Mail list logo
