Am Donnerstag, dem 26.12.2024 um 13:48 +0200 schrieb Slava Shpitalny:
> Do you happen to have any updates on this issue?
Hi,
unfortunately not, the only thing I found is this in "man 2 open":
...
EINTR While blocked waiting to complete an open of a slow device
(e.g., a FIFO; see fifo(7)), the
Am Sonntag, dem 01.12.2024 um 21:59 +0100 schrieb Alexander Farber:
> But I am yet not sure how to enable listening at localhost again
Instead of using a TCP/IP connection, why not use the unix socket to
connect to your database [1]?
[1] https://jdbc.postgresql.org/documentation/use/#unix-sockets
Am Mittwoch, dem 20.09.2023 um 13:11 +0200 schrieb Laurenz Albe:
> Is that an NFS mount? What are the mount options?
>
> Yours,
> Laurenz Albe
No mount at all.
Just the docker container filesystem using the overlay2 storage driver,
there is nothing externally mounted in that container, the data
Hi,
I am running the postgres docker image with that version:
2023-09-20 10:36:32.478 CEST [1] LOG: starting PostgreSQL 13.12 (Debian
13.12-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14)
12.2.0, 64-bit
2023-09-20 10:36:32.564 CEST [1] LOG: listening on IPv4 address "0
Am Mittwoch, dem 06.09.2023 um 20:42 +0200 schrieb Imre Samu:
> Maybe you have to increase the "*--stop-timeout" value
That is totally unrelated in my case, it is an anonymous volume anyway
which gets created on start and deleted afterwards.
Torsten
Am Mittwoch, dem 06.09.2023 um 12:04 +0200 schrieb Erik Wienhold:
> > I am running that one (official docker image)
> >
> > PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu,
> > compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
>
> Have you also tried with 13.12?
Yes, b
Am Mittwoch, dem 06.09.2023 um 10:21 +0200 schrieb Laurenz Albe:
> You are lucky that the corrupted table is one that holds data that
> can be rebuilt.
It is a test instance / container anyway which is deleted afterwards
and can be setup again as often as I want.
But how is that corruption happen
Hi,
I am running that one (official docker image)
PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
and one of my nightly jobs reported that error yesterday when running
an "ANALYZE":
FEHLER: doppelter Schlüsselwert ver
But you should do that according to the documentation:
...
After restoring a backup, it is wise to run ANALYZE on each database so the
query optimizer has useful statistics.
...
Am Mittwoch, den 11.03.2020, 11:46 -0500 schrieb Jerry Sievers:
> If your site can afford a restart after the bulk load,
>
> 1. Clean shutdown.
> 2. pg_resetwal
> 3. Start
>
> That should leave you with a very small N WAL files, perhaps just 1,
> though I've not run it lately to reverify.
Thank
Am Mittwoch, den 11.03.2020, 15:45 + schrieb Simon Riggs:
> The size of the task varies, so sometimes takes longer than 60s,
> depending
> upon your hardware.
Yes that's what I am observing and why I am asking if there is some
select statement or command which triggers that task and returns af
Am Mittwoch, den 11.03.2020, 08:42 -0600 schrieb Michael Lewis:
> I don't know the answer to your stated question. I am curious if you
> have
> set wal_level = minimal and if not, if that would be appropriate for
> your
> use case and might render your concern a non-issue.
Hi Micheal,
I am alread
Hi,
I am building a docker image with a postgresql 12.2 instance and while
doing so and importing a dump and running some update scripts wal size
is increasing.
When finished I don't need all those wal files anymore and tried to
force the daemon to clean them up and tried this:
select pg_swi
13 matches
Mail list logo
