> On 25 Sep 2017, at 09:51 , hvjunk wrote:
>
> Good day,
>
> See the sequence below, Postgresql 9.6.5 on Debian using the postgresql
> repository.
>
> Question: Is this expected behaviour?
I guess it might be, but the “bug” is that the excessive/unused sequence is
Good day,
See the sequence below, Postgresql 9.6.5 on Debian using the postgresql
repository.
Question: Is this expected behaviour?
postgres@tracsdbhvt01:~$ cat test-serial.sql
create database test;
\c test
create table test_serial ( teststring varchar(5));
alter table test_serial add colum
Hi there,
I’ve previously done ZFS snapshot backups like this:
psql -c “select pg_start_backup(‘snapshot’);”
zfs snapshot TANK/postgresql@`date ‘+%Ymd’`
psql -c “select * from pg_stop_backup();”
Reading the PostgreSQL9.6 documentation, the advice/future is to use the
non-exclusive method, whe
> On 22 Jun 2017, at 04:44 , Lucas Possamai wrote:
>
>
>
> 2017-06-22 14:16 GMT+12:00 hvjunk <mailto:hvj...@gmail.com>>:
>
>> On 22 Jun 2017, at 4:06 AM, Lucas Possamai > <mailto:drum.lu...@gmail.com>> wrote:
>>
>>
>>
> On 22 Jun 2017, at 4:06 AM, Lucas Possamai wrote:
>
>
>
> 2017-06-22 13:54 GMT+12:00 hvjunk <mailto:hvj...@gmail.com>>:
> Hi there,
>
> I was hoping for a method (like archive_command) to handle logfile
> processing/archiving/compression, but
Hi there,
I was hoping for a method (like archive_command) to handle logfile
processing/archiving/compression, but unless doing it the logrotate way, I
don’t see anything that postgresql provides. Is that correct?
The closest I could find is: pg_rotate_logfile()… but here my question is where
