Hello,
I bump this thread up, I hope to have more reaction :)
TL;DR:
* We can't perform PITR on a cluster without any activity since 13
* It seems creating restore point doesn't record a timestamp in wal.
Thanks
--
Adrien NAYRAT
On Tue, Jan 03, 2023 at 01:52:17PM +0800, Julien Rouhaud wrote:
> Resetting the data adds some noticeable overhead as newly added entries will
> need to generate a normalize query string and so on. What most people do is
> taking regular snapshots of pg_stat_statements (and other stats) view and t
On Mon, Jan 9, 2023 at 10:59 AM Adrien Nayrat
wrote:
>
> * We can't perform PITR on a cluster without any activity since 13
> * It seems creating restore point doesn't record a timestamp in wal.
>
I have a cron job that runs this every 5 minutes:
SELECT txid_current() WHERE
(pg_last_committed_x
Hello,
Please note: I'm talking about the user and group "postgres" in the
Linux OS and not in the PostgreSQL server.
We're compiling PostgreSQL from source (actually 14.1) and distribute that
to our customers. They're asked to setup user and group "postgres"
before creating the cluster. As now
On 2023-01-09 07:41, Matthias Apitz wrote:
Hello,
Please note: I'm talking about the user and group "postgres" in the
Linux OS and not in the PostgreSQL server.
We're compiling PostgreSQL from source (actually 14.1) and distribute that
to our customers. They're asked to setup user and group "po
On 1/9/23 07:41, Matthias Apitz wrote:
Please note: I'm talking about the user and group "postgres" in the
Linux OS and not in the PostgreSQL server.
We're compiling PostgreSQL from source (actually 14.1) and distribute that
to our customers. They're asked to setup user and group "postgres"
befo
> On 09/01/2023 13:41 CET Matthias Apitz wrote:
>
> Hello,
>
> Please note: I'm talking about the user and group "postgres" in the
> Linux OS and not in the PostgreSQL server.
>
> We're compiling PostgreSQL from source (actually 14.1) and distribute that
> to our customers. They're asked to setup
El día Montag, Januar 09, 2023 a las 08:15:33 -0500, Joe Conway escribió:
> On 1/9/23 07:41, Matthias Apitz wrote:
> > Please note: I'm talking about the user and group "postgres" in the
> > Linux OS and not in the PostgreSQL server.
> >
> > We're compiling PostgreSQL from source (actually 14.1)
On 1/9/23 07:15, Joe Conway wrote:
On 1/9/23 07:41, Matthias Apitz wrote:
Please note: I'm talking about the user and group "postgres" in the
Linux OS and not in the PostgreSQL server.
We're compiling PostgreSQL from source (actually 14.1) and distribute that
to our customers. They're asked to
On 1/9/23 09:11, Ron wrote:
On 1/9/23 07:15, Joe Conway wrote:
On 1/9/23 07:41, Matthias Apitz wrote:
Please note: I'm talking about the user and group "postgres" in the
Linux OS and not in the PostgreSQL server.
We're compiling PostgreSQL from source (actually 14.1) and distribute that
to our
Are there any limits on the number of records in
the postgresql/12/main/pg_multixact/members directory? We have a database
that has grown to tens of thousands of files in this directory during an
autovacuum after a large data purge. It shrank after the autovacuum
completed.
Martin Ritchie
*Geotab*
At Thu, 29 Dec 2022 13:52:18 +0300, Дмитрий Цветков
wrote in
> I'm trying to write my first extension and open a table in it.
> I use check_password_hook and my function executes at the moment of
> changing user password.
>
> But if I try to open a table inside this function, I get Segmentation
12 matches
Mail list logo
