. And
as I see it is not only in the CSV logs, also in the none CSV logs I
have.
Is there a way to convince Postgres to write the date/time with
numerical time zone values to the log files?
Regards,
Michael
Hi
-Original Message-
From: pgsql-general-ow...@postgresql.org
On 09/22/2015 06:31 AM, Michael Zoet wrote:
Hi Charles,
thanks for the quick response and it looked promising but did not work
as expected.
I can set the datestyle to ISO on database level but this does not seem
to effect the way the CSV logs are written. I still get 2015-09-22
13:06:01.658
Hi Tom,
Michael Zoet writes:
Is there a way to convince Postgres to write the date/time with
numerical time zone values to the log files?
Try something like
log_timezone = '<-0400>+4'
OK this points me in a directions I haven't read anything about in the
Postgres
, it will
always print me the name if I use a name for the time zone. And that
is the no go for Logstash. So I really need a numerical value to parse
it with Logstash.
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e <+>+0, ie force it to
print in GMT always.
That's it! Having everything in numeric UTC + seems the easiest
solution. With that I shouldn't have any parsing problems with
Logstash. So I do not need to think about the offset. Great and
obvious :-).
Michael
--
Sent v
ing the blame in
pg_dump. FWIW, that's something I am investigating on this thread of
-hackers:
http://www.postgresql.org/message-id/20150926132237.gj5...@alap3.anarazel.de
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ough data replayed, you should make the WAL
position of the master necessary for the transaction of the standby
something that your application is aware of.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sat, Oct 3, 2015 at 10:20 PM, Madovsky wrote:
>
>
> On 10/3/2015 4:48 AM, Michael Paquier wrote:
>>
>> On Sat, Oct 3, 2015 at 8:09 PM, Madovsky wrote:
>>>
>>> I would like to fix a issue I'm facing of with the version 9.4 streaming
>>>
On Sun, Oct 4, 2015 at 6:38 AM, Madovsky wrote:
> On 10/3/2015 6:55 AM, Michael Paquier wrote:
>> On Sat, Oct 3, 2015 at 10:20 PM, Madovsky wrote:
>> Requesting the master would be necessary, still I don't really get why
>> you don't want to query the master fo
(Seems like you forgot to push the Reply-all button)
On Sun, Oct 4, 2015 at 7:01 PM, Madovsky wrote:
> On 10/3/2015 3:30 PM, Michael Paquier wrote:
>> and no reason is given to justify *why* this would be needed in your case
> reason for a choice can be often an issue for other :D
&
uum_freeze_table_age = 15000
So, do I need to run vacuum freeze on those tables? Also, if
autovacuum_freeze_max_age is commented, does it still mean that the default
is 200M?
Thanks,
Michael
atch regarding that for 9.6:
https://commitfest.postgresql.org/6/320/
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
within
> my C function. Can anyone provide some advice on how to do this?
What you are looking for is in miscadmin.h:
username = GetUserNameFromId(GetSessionUserId());
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your s
ads to:
...
checking openssl/ssl.h usability... no
checking openssl/ssl.h presence... no
checking for openssl/ssl.h... no
configure: error: header file is required for OpenSSL
Any ideas...?
Thanks in advance!
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
ds to:
...
checking openssl/ssl.h usability... no
checking openssl/ssl.h presence... no
checking for openssl/ssl.h... no
configure: error: header file is required for OpenSSL
Any ideas...?
Thanks in advance!
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
e, nor have there been any
database shutdowns other than the panics.
I would be very grateful for any insights as to what may have caused this,
and how best to recover stable operation.
Best regards,
Michael Robinson
>From http://www.postgresql.org/download/linux/redhat/ comes the following
quote:
--
Due to policies for Red Hat family distributions, the PostgreSQL
installation will not be enable
Forgive my ignorance, but I'm new to PostgreSQL. Regarding installation,
I'm trying to understand some of the differences between Red Hat, Ubuntu,
and OpenSUSE. My goal is to set up a self-contained lab instance for
learning on each distribution. So, I assume I'll need both the client and
server on
to answer. If I were you I'd
begin first by letting more time for the repack operation to complete.
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
at includes backup and history files. Perhaps we would
gain in clarity by saying "WAL file segments, including .partial
segments" in the docs, and not just "WAL files". Thoughts?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, Nov 3, 2015 at 11:29 PM, Albe Laurenz wrote:
> Michael Paquier wrote:
>>> So, as Albe posted pg_archivecleanup is only cleaning up the WAL files, not
>>> the auxiliary files. The WAL files would be the ones with no extension and a
>>> size of 16 MB(unle
On Wed, Nov 4, 2015 at 10:16 PM, Jiří Hlinka wrote:
> I'm on pg_repack 1.3.2 (latest sable, no devel version available to check
> if it is already fixed).
>
> Michael: your memories are fresh and clear :-), yes, it is part of a
> cleanup rollback. The problem is, that the pgr
On Wed, Nov 4, 2015 at 7:16 PM, Albe Laurenz wrote:
> Michael Paquier wrote:
>>>> The docs mention that "all WAL files" preceding a given point are
>>>> removed, personally I understand that as "all 16MB-size segments shall
>>>> die", h
on
working on the trigger being dropped to finish. We could say that
there is a deadlock if the transaction inserting data to repack.log%
is actually holding a lock that conflicts with the trigger being
dropped.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
Below is from my OpenSUSE command line. I only installed the first package,
but both say, "Installed: Yes". Why is this? Are they really the same
package?
linux-srqm:~ # zypper info postgresql
Loading repository data...
Reading installed packages...
Information for package postgresql:
-
SSIS can be used to migrate data from MSSQL to Postgres and back.
It is native for MS SQL
You can use PG ODBC driver
http://www.postgresql.org/ftp/odbc/versions/msi/
or Devart ODBC driver
https://www.devart.com/odbc/postgresql/
On Wed, Nov 11, 2015 at 9:27 AM, Scott Mead wrote:
>
> On Wed, Nov 1
In Ubuntu 14.10, there are three variations of the postgresql.conf
configuration file, as follows:
/var/lib/postgresql/9.4/main/postgresql.auto.conf
/usr/lib/tmpfiles.d/postgresql.conf
/etc/postgresql/9.4/main/postgresql.conf
What is the difference between these files and which is the correct one
ect upper(gen_random_uuid()::text);
upper
--
057A3BC2-0E62-4D68-B01A-C44D20F91450
(1 row)
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
restart
the error handling is tricky if you just have control via psql. How
could you start a node that has been stopped during a restart but
could not boot up. Take the example of an incorrect parameter value
that has been added when the node was up via ALTER SYSTEM...
--
Michael
--
Sent
On Fri, Jun 3, 2016 at 8:48 AM, David G. Johnston
wrote:
> On Thu, Jun 2, 2016 at 7:39 PM, Michael Paquier
> wrote:
> I was focused on admin task due to the pg_ctl (not sure you'd want to run
> that via psql...) but if you have shell script applications you want to run
>
> Can I not wrap it around another user defined function with SECURITY DEFINER
> and grant privilege to specific users who can use it?
pg_ls_dir() has a check on superuser() embedded in its code.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sat, Jun 4, 2016 at 11:34 PM, Vik Fearing wrote:
> On 03/06/16 04:32, Michael Paquier wrote:
>> pg_ls_dir() has a check on superuser() embedded in its code.
>
> So what? That's what SECURITY DEFINER is all about.
Yes you are right. I missed completely the point :)
Thanks
On Mon, Jun 6, 2016 at 9:51 PM, Stephen Frost wrote:
> * Vik Fearing (v...@2ndquadrant.fr) wrote:
>> On 03/06/16 04:32, Michael Paquier wrote:
>> > On Fri, Jun 3, 2016 at 11:23 AM, Sameer Kumar
>> > wrote:
>> >> On Fri, Jun 3, 2016 at 4:30 AM Stephen Frost
I am working with a system that uses JDBC and JNDI-based connection
pooling. There are currently many organizations that use the system. Each
of the organizations has multiple, individual system users.
Currently, each entity has its own database and a corresponding
application-based datasource and
we
can rely on I am afraid. Which version of Postgres 9.5 are you using?
9.5.3? If you use 9.5.2 are you still seeing the problem? We may be
seeing a side-effect of a3c17b2a here.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ode paths for a reason or another
that may result in a leak if this code path is taken repeatedly and
that the memory used is wasted out.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pg
Pgbouncer worked fine for this. Thanks.
On Wed, Jun 8, 2016 at 1:12 PM, Sameer Kumar
wrote:
>
>
> On Thu, 9 Jun 2016, 12:50 a.m. Michael McInness,
> wrote:
>
>> I am working with a system that uses JDBC and JNDI-based connection
>> pooling. There are currently many
On Fri, Jun 10, 2016 at 6:06 AM, Melvin Davidson wrote:
> as the developers have a nasty habit of changing pg_catalog
> tables/columns.
... When necessary to improve the quality of the project and the user
experience.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-g
g_dump.
Schemas can be part of the extension definition and be linked to it,
and tables created on top of the schema defined in the extension
should really be dumped..
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http:/
On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués wrote:
> Hi Michael,
>
> 2016-06-15 5:00 GMT-03:00 Michael Paquier :
>> Martin wrote:
>>> I wonder if this is the desirable way of handling pgq, or if those
>>> tables should be dumped. I'm starting to think tha
On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués wrote:
> El 16/06/16 a las 00:08, Michael Paquier escribió:
>> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
>> wrote:
>>>
>>> How would the recovery process work? We expect the schema to be there
>>>
m/ossc-db/pg_bulkload
If you have problems with it, you should directly contact the folks in
charge of maintaining this project, aka NTT-OSSC, with more details
about the failure. Without more information, anybody would have a hard
time to analyze your problem.
--
Michael
--
Sent via pgsql-genera
: *** [installcheck] Error 2
Which test are you trying to run? That's not from the in-core source
tree, right? And on which version of Postgres is this attempt tried?
With this level of details that's hard to know what's going on, one
can just guess that PreventTransactionChain is be
your plugin per the context message.
Do you have an SQL sequence that allows to reproduce the problem? I
recall playing with a couple of data types with my own plugin but I
never noticed that.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
;
//else if (typisvarlena && VARATT_IS_EXTERNAL_ONDISK(origval))
// appendStringInfoString(s, "unchanged-toast-datum")
Uncomment that.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
done at the creation of a checkpoint, for a standby that's when a
restart point is created. See where KeepLogSeg() in xlog.c.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Mon, Jun 27, 2016 at 9:21 AM, 유성열 wrote:
> Please, I want to unsubscribe your email. Delete my mail address in your
> mail list, please...OMG..
>
You can do it by yourself here:
https://www.postgresql.org/community/lists/subscribe/
There is an unsubscribe option.
--
Michael
d.
Honestly, you can only be sure that a backup is working correctly
after reusing it. You could always do some validation of the raw
backup contents, but you need at the end the WAL applied on top of it
to be able to check the status of a server that has reached a
consistent point.
--
Michae
system that is a pre-stage of the production stage, where the backups
are replayed and checked with an application that replays the patterns
of the production application. Applying extra checks on top of that is
good as well: pg_dump, data checksums, index consistency checks (this
makes regret
n flushed to disk
on the standby, so it would not be lost in case of a master crash.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
he backup
you took is likely useless. It may not be able to reach a consistent
state.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
vel of locking could be used,
ShareLock is a strong one, taken when you want to be sure that there
are schema changes for example.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Mon, Jul 18, 2016 at 7:08 PM, sudalai wrote:
> thank u.
> why (select * from pg_logical_slot_peek_changes('slot',NULL,1) ) take share
> lock ?
> any idea ?
My guess is that this lock comes from your plugin code. Please double-check it.
--
Michael
--
Sent via pgsq
he report! I haven't looked at the problem in details yet,
but my guess is that this is owned by Stephen Frost. test_pg_dump does
not cover sequences yet, it would be visibly good to get coverage for
that. I am adding an open item as well.
--
Michael
--
Sent via pgsql-general mailing lis
447...@tornado.leadboat.com
I am not sure what's Stephen's status on this item, but I am planning
to look at it within the next 24 hours.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
serial column created in an extension where the sequence is
dropped from the extension afterwards.
--
Michael
diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c
index 08c2b0c..0278995 100644
--- a/src/bin/pg_dump/pg_dump.c
+++ b/src/bin/pg_dump/pg_dump.c
@@ -6037,6 +6037,8 @@ getOwne
figuration file was the same for 9.3 and 9.5, except for the
> "chekpoint segment" that has been deprecated.
Which value are you using for max_wal_size and min_wal_size? And which
value of checkpoint_segments did you use previously? This could
influence the checkpoint frequency.
--
heckpoint_segments) * 16MB
> #min_wal_size = 80MB
>
> though I tried max_wal_size = 3GB (default is 1GB) and did not notice any
> improvment.
And do you see changes if you increase min_wal_size? This will
increase the number of WAL segments recycled instead of removed at
each checkpoint.
--
y case to on, as is
full_page_writes.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
://stackoverflow.com/questions/38750898/build-or-install-pg-loader-on-windows
<http://stackoverflow.com/questions/38750898/build-or-install-pg-loader-on-windows>
I didn't get a response there, so I do hope someone here might be able to help.
Thanks,
Michael
Michael Sheaver
ther stable state. I got that integrated into some of the things I
work on, and nobody complains about it.
[1]: https://github.com/vmware/pg_rewind
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
uot;status": true},
"dashboard":{"status": false},
"help": {"status": true}}'::jsonb);
key| ?column?
---+--
chat | true
help | true
admin | true
accounts | true
calendar | false
con
s really the same issue... See here for more details:
https://www.postgresql.org/message-id/20160712083220.1426.58...@wrigleys.postgresql.org
If you have ideas about making a difference between a real permission
error and STATUS_PENDING_DELETE, that would be great.
--
Michael
--
Sent via pgsql-
TE BY, DISTRIBUTED or DISTSTYLE.
By the way, note that the mailing lists of Postrges-XL are here:
http://www.postgres-xl.org/support/
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
facing a corruption:
https://wiki.postgresql.org/wiki/Corruption
Be sure that you have a clean backup of your database first!
> PosgreSQL version is 9.2.4.
You are missing a couple of years worth of bug fixes here..
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@pos
are taking a lot of risks here by only using 9.2.4.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
hat is this "global/pg_filenode.map" for?
It is a relation map file referring a list of OID -> relfilenode. You
can look at the comments on top src/backend/utils/cache/relmapper.c
for more details.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To m
il now.
No, it's not. This should not happen. And this means that your data
folder is facing some corruption.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
on!) got clobbered afterwards.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Sqlite this handled as:
> UPDATE OR IGNORE table SET
> UPDATE OR REPLACE table SET
>
> And so on
>
> See https://www.sqlite.org/lang_update.html.
>
> Can Postgres do this?
Somewhat with a plpgsql function, but with a native UPDATE query, the
answer is no.
--
Michael
--
pment strategy to implement user requests.
Gitkraken is simply awesome and my go-to GUI for VCS.
An added benefit of this particular toolset is that they work equally well on
Mac and Windows.
Michael Sheaver
mshea...@me.com
> On Sep 3, 2016, at 9:28 AM, Mike Sofen wrote:
>
> From:
t you trigger a promotion which would make the master reach the
timeline 3? And are you sure that 0003.history is not in the
archives?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ossible, and things
are kept compatible as much as possible. Personally I find deploying a
backup of PGDATA instead of reusing an existing PGDATA with older
binaries after it has run with newer binaries a more iron-solid
approach, and I've learnt to be careful with such things..
--
Michael
-
using dumpbin /headers
and by looking for "Dynamic base". Also, you could redirect the logs
to pg_log by modifying manually postgresql.conf before starting it.
This would provide more information regarding why postgres is not
running.
--
Michael
--
Sent via pgsql-general mailing lis
I have done some research after converting my database from MySQL 5.6 to
PostgreSQL 9.6 (the best move I have ever made), and the consensus I found can
be summed up as:
1. Never, neve, never use VARCHAR or even CHAR
2. Always always, always use TEXT
Unless, that is, you have some kind of edge c
some
truth to the old adage that we must learn from our own mistakes. :)
> On Sep 26, 2016, at 8:46 AM, Michael Sheaver wrote:
>
> I have done some research after converting my database from MySQL 5.6 to
> PostgreSQL 9.6 (the best move I have ever made), and the consensus I found
to be the cause.
What are the files in pg_xlog/archive_status? Do see a lot of .ready
entries? Perhaps you could de-bloat things by using archive_command =
'/bin/true' (REM on Windows as far as I recall).
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
ecords. Note that replication
slots created on standbys are initialized from the last checkpoint
redo record, so you could take advantage of this property before
promoting a standby.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your s
been known to kill screen/tmux/nohup
> processes when a user logs out in its keenness to clean up but
> that may be clutching at straws.
systemd sometimes has fun removing semaphores. See here for example:
https://www.postgresql.org/message-id/cak7teys9-o4bterbs3xuk2bffnnd55u2sm9j5r2fi7v6bhj..
nd until its
partition gets full.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> problem for this?
I find the references to pglz quite troubling, particularly by reading
that this data type visibly uses its own compression logic.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.o
#x27;t qualify (in very exceptional cases they might but this
> issue is a routine performance enhancement). Basically you have to
> decide to update or stay with 9.5.
Another possibility is to patch and build yourself Postgres if you are
still willing to use that with a given version. But as that&
On Wed, Oct 12, 2016 at 10:04 AM, Dylan Luong wrote:
> I am new to pgpool.
You may want to ask directly on the mailing lists of pgpool, even if
Tatsuo-san or anybody involved in it are looking at this mailing list:
http://pgpool.net/mediawiki/index.php/Mailing_lists
--
Michael
--
Sent
gt; I'm not sure announcements of commercial software updates belong on the
> pgsql-general email list. if every vendor of apackage with postgres
> support posted announcements of each incremental update, we'd be buried in
> spam.
Yeah.. If it applies somewhere that would be pgsql
d, but the choice
here impacts performance.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
; Is there a plan to add this feature on future version ?
I don't recall plans in this area. Maybe there's room for a
jsonb_compact(). core has already jsonb_pretty(), and that would be
what has the less overhead when doing the binary/text conversion.
--
Michael
--
Sent via pgsql-gen
f random ones
should not matter much (never tried pg_sample to be honest).
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ical tables, without the TRUNCATE trigger
bit.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
n that this file is
> in fact there (any more).
It is never a good idea when you are trying to restore from a backup,
backup_label contains critical information when restoring from a
backup, so you may finish with a corrupted data folder.
--
Michael
--
Sent via pgsql-general mailing list (pgsq
w standby. pg_rewind will be
successful to run only if the master has kept WAL segments from the
last checkpoint record where WAL forked when standby has been
promoted.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
need to make auto vacuum more log-verbose first.
Yeah. If you are using 9.5 or newer versions, you could set
log_autovacuum_min_duration to 0 for this relation and avoid a lot of
noise in your logs. pg_stat_user_tables and pg_stat_all_tables also
contain information regarding the last time autovacu
our hardware
here.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Mon, Oct 24, 2016 at 2:20 PM, Dasitha Karunajeewa
wrote:
> Hi Michael,
>
> Thanks a lot for the information. I am totally new to Postgres clustering. I
> have follow up the below-attached article.
> https://www.digitalocean.com/community/tutorials/how-to-set-up-master-slave
es. So if
you would like to remove a standby from a cluster. You just need to
basically stop it, then remove its data folder. And you are done.
There is no complicated science here.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
but this seems to be not the case, is this expected?
This is on 9.5.4, self-compiled.
Michael
--
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax: +49 2166 9901-100
Email: michael.ba...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trom
to hack
your own thing, and that would finish by being more performant as
their is not need to do a post-receive format change of the data
received by a single change. Now regarding the stability of the thing,
the code is in a pretty nice shape.
--
Michael
--
Sent via pgsql-general mailing list (
ical
decoding, and as far as I recall it uses its own protocol to replicate
changes. I never had a look at it in details but that may be something
to look into if you are looking for some story in this area.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postg
be
binary-compatible with 9.6. For consistency's sake, you may want to
recompile it anyway.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
"
>
> I guess archive_timeout forcing to switch new WAL file, see this :
> https://www.postgresql.org/docs/devel/static/runtime-config-wal.html#GUC-ARCHIVE-TIMEOUT
Out of curiosity, which version are you using? That's 9.6, no?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-gen
S735Bd2RzApNqSNJVietAC=6kfkyv_45d...@mail.gmail.com#CAB7nPqQcPqxEM3S735Bd2RzApNqSNJVietAC=6kfkyv_45d...@mail.gmail.com
My guess is that you are using 9.6 because wal_level = archive is
equivalent to hot_standby, and the checkpoint skip logic is broken
because of standby snapshots happening in the b
101 - 200 of 3411 matches
Mail list logo
