I'm not sure, does it helps you but read this:
https://www.cybertec-postgresql.com/en/b-tree-index-improvements-in-postgresql-v12/
"Since upgrading with pg_upgrade does not change the data files, indexes
will still be in version 3 after an upgrade"
I reindexed all my database, when did upgrade
Hi,
It's a typical error for brand new setup. After new backup setup do
$ barman switch-xlog --force --archive testdb
br
Kaido
On Wed, 10 Jan 2024 at 15:58, duc hiep ha wrote:
> Dear All,
>
> I am trying to use Barman to back up PostgreSQL, which is running in a
> Podman container. However,
Add a pg binary path to script
br
Kaido
On Mon, 4 Dec 2023 at 18:13, Alan Hodgson wrote:
> On Mon, 2023-12-04 at 11:07 -0500, Ron Johnson wrote:
>
> PG 9.6.24 (Yes, it's EOL.)
>
> When running "vacuumdb -p5433 -j4 --analyze tap_d" from a bash prompt, it
> works as expected:
> $ vacuumdb -p5433
xid in wal should be transaction id. It is one option (with pid) for log
line prefix
br
Kaido
On Tue, 24 Jan 2023, 21:37 David G. Johnston,
wrote:
> On Tue, Jan 24, 2023 at 12:30 PM kaido vaikla
> wrote:
>
>> Hi
>> Take a look at parameter
>> log_line_prefix
Hi
Take a look at parameter
log_line_prefix
br
Kaido
On Tue, 24 Jan 2023, 20:36 Sergey Burladyan, wrote:
>
> Hi, All!
>
> Is it possible to associate a WAL record with it session/process id?
>
> For example, if I have this record in WAL:
> rmgr: Standby len (rec/tot): 42/42, tx:
Talking about fsfreeze and blocksize are not relevant in your case at all.
You can't make a backup this way any way. According your mail,
you are playing with database recovery after crash. Is pg crash proof? Yes (
https://www.postgresql.org/docs/current/wal-intro.html).
You can use this solution
