n 11/30/23 20:43, Matthias Apitz wrote:
> > El día jueves, noviembre 30, 2023 a las 02:10:25p. m. -0800, Adrian
> Klaver escribió:
> >
> >> On 11/30/23 12:35, Adrian Klaver wrote:
> >>> On 11/30/23 10:35, Adrian Klaver wrote:
> >>>> On 11/3
a strange case
El jue., 30 nov. 2023 16:23, Adrian Klaver
escribió:
> On 11/30/23 05:37, Loles wrote:
> > Hi!
> >
> > I have this situation on a server that is giving me problems.
> >
> > postgres@hostname:~$ pg_lsclusters
> > Ver Cluster Port Status Own
/var/lib/postgresql/14/main
/var/log/postgresql/postgresql-14-main_old.log
Start, up the two cluster.
El jue, 30 nov 2023 a las 18:01, Adrian Klaver ()
escribió:
> On 11/30/23 08:46, Loles wrote:
> > Yes, it exists but it is obsolete. The files and directories are all
> > dated 2
Yes, it exists but it is obsolete. The files and directories are all dated
2022.
It was obsolete and no longer valid, it could be deleted. Only the main
cluster is correct.
El jue, 30 nov 2023 a las 17:43, Adrian Klaver ()
escribió:
> On 11/30/23 08:37, Loles wrote:
> > Every time I
Every time I stop the main_old cluster with sudo pg_ctlcluster stop 14
main_old, both are stopped. And when I raise sudo pg_ctlcluster start 14
main, both are raised.
I don't know how I got into this situation and I don't know how to resolve
it.
El jue, 30 nov 2023 a las 17
Hi!
I have this situation on a server that is giving me problems.
postgres@hostname:~$ pg_lsclusters
Ver Cluster Port Status OwnerData directory Log file
14 main 5432 online postgres /var/lib/postgresql/14/main
/var/log/postgresql/postgresql-14-main.log
14 main_old 5432 on
Ok, now I know.
Thank you very much to all!!
El lun, 17 may 2021 a las 8:37, David G. Johnston (<
david.g.johns...@gmail.com>) escribió:
> On Sunday, May 16, 2021, Loles wrote:
>
>> I don't understand why the server starts that process if I'm not using
>> rep
d.
El lun, 17 may 2021 a las 7:41, Dilip Kumar ()
escribió:
> On Mon, May 17, 2021 at 12:18 AM Loles wrote:
> >
> > Hi!
> >
> > Let's see if someone can answer my question.
> >
> > In a default PostgreSQL 13 installation, starting the server starts a
>
Why the Server startup this background process?
Isn't a mandatory process.
And what's the logical replicación Launcher do?
El dom., 16 may. 2021 21:21, Ron escribió:
> On 5/16/21 1:47 PM, Loles wrote:
> > Hi!
> >
> > Let's see if someone can answ
Hi!
Let's see if someone can answer my question.
In a default PostgreSQL 13 installation, starting the server starts a
process called "logical replication launcher".
I know what logical replication is but I don't know what this process does
on the server.
Even if you change the default setting
One thing is the number of records in the table and another is the current
value of the sequence.
Execute:
select max (field) from bobo.menu_pages;
In both master and slave server.
What give you back?
"field" is the data that belongs to the sequence.
El lun., 15 feb. 2021 18:55, Paolo Saudi
I would try..
Read the server log
Try copying to another simpler path like C:\wal_archives
Maybe blankspaces give problems
Have you forgotten to configure any other parameter like max_wal_senders?
I hope some of this hemos you
Loles
El jue., 29 oct. 2020 20:36, Atul Kumar escribió:
>
12 matches
Mail list logo
