On 1/23/19 8:41 PM, Alex Morris wrote:
On 1/23/19 19:15, Stephen Frost wrote:
Greetings,
* Alex Morris (alex.mor...@twelvemountain.com) wrote:
This question may simply be my ignorance of what piece of the systemd /
systemctl puzzle needs attention. Any clues are appreciated.
The simplest ap
On 1/23/19 19:15, Stephen Frost wrote:
Greetings,
* Alex Morris (alex.mor...@twelvemountain.com) wrote:
This question may simply be my ignorance of what piece of the systemd /
systemctl puzzle needs attention. Any clues are appreciated.
The simplest approach is to just modify the postgresql.
Greetings,
* Alex Morris (alex.mor...@twelvemountain.com) wrote:
> This question may simply be my ignorance of what piece of the systemd /
> systemctl puzzle needs attention. Any clues are appreciated.
The simplest approach is to just modify the postgresql.conf file in
/etc/postgresql/9.5/main t
Greetings,
This question may simply be my ignorance of what piece of the systemd /
systemctl puzzle needs attention. Any clues are appreciated.
Using postgreSQL version 9.5 as obtained from ubuntu repo. Install was
fine. initdb and subsequent database use is fine.
Nothing is out of the o
Tom Lane writes:
> Alban Hertroys writes:
>
>> Our current development database server is running a bit low on diskspace,
>> so I dropped an old but rather large database with the intention of
>> claiming back some space. However, the space remains claimed.
>> This server was upgraded from PG1
On Wed, 2019-01-23 at 18:58 +0100, Ivan Voras wrote:
> And, the actual question: how to monitor the WAL replay process?
> Currently, the recovery.conf file is sitting there, with the database
> running, but pg processes are idle, and pg_stat_activity doesn't list
> anything which appears to be rela
Hello,
I got a sort of POLA violation moment today - a colleague has restored a
PITR archive up to a point in time, and when the developers looked at the
data, it looked wrong - as it if wasn't from that particular time. Later,
he told me he got an error trying to use pg_dump to extract the desire
"Tom Lane" wrote on 2019-01-23 16:02:01:
> Alban Hertroys writes:
> > Our current development database server is running a bit low on
diskspace,
> > so I dropped an old but rather large database with the intention of
> > claiming back some space. However, the space remains claimed.
> > This s
Thanks, I see... So if I understand it correctly - since I have quite big
>> partitions like ~30 GB each in one parent table and from ~1GB to ~5 GB in
>> several others I presume I had to set wal_keep_segments to some really high
>> number and stop our security cronjob cleaning old WAL segments (be
Alban Hertroys writes:
> Our current development database server is running a bit low on diskspace,
> so I dropped an old but rather large database with the intention of
> claiming back some space. However, the space remains claimed.
> This server was upgraded from PG10 to PG11 using pg_upgrade'
Hi all,
Our current development database server is running a bit low on diskspace,
so I dropped an old but rather large database with the intention of
claiming back some space. However, the space remains claimed.
This server was upgraded from PG10 to PG11 using pg_upgrade's --link
option.
I s
Hi guys, thank you very much for all information. I learned my lesson
regarding cronjob cleaning old WAL logs...
There is one other interesting problem I have found today and I would like
to ask you about you opinion.
On logical master I found this morning big flood of these messages in
postgresql
12 matches
Mail list logo
