On Fri, Apr 28, 2017 at 4:39 PM, Andrew Kerber
wrote:
> I am a fairly experienced Oracle DBA, and we are starting to move in to
> the PostgreSQL world. I would expect the standard monitoring items are
> required for mission critical postgres apps, Ie, disk space, wal
On Tue, May 3, 2016 at 3:22 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Jan Keirse <jan.kei...@tvh.com> writes:
> > I have a table that used to contain all data.
> > because it grew too big I added a partition trigger a long time ago and
> > since than all new d
Hello,
I have a table that used to contain all data.
because it grew too big I added a partition trigger a long time ago and
since than all new data was added to small partitions. By now all data in
the original parent table has become obsolete and was deleted, however the
disk space cannot be
On Tue, Aug 18, 2015 at 1:00 PM, Jimit Amin jimitam...@gmail.com wrote:
Can I know normal, aggressive, best parameter settings for PostgreSQL.conf
file for particular hardware.
Like Linux x86_64 , 8 GB Ram
, Linux x86_64 , 126 GB Ram
There's no generic answer because it depends on what
On Tue, Aug 4, 2015 at 6:24 AM, William Dunn dunn...@gmail.com wrote:
Hello Jan,
I think your calculation is slightly off because per the docs when
PostgreSQL comes within 1 million of the age at which an actual wraparound
occurs it will go into the safety shutdown mode. Thus the calculation
On Thu, Jul 30, 2015 at 2:56 PM, Adrian Klaver
adrian.kla...@aklaver.com wrote:
On 07/30/2015 02:55 AM, Jan Keirse wrote:
Hello,
we have some very write heavy databases and I have our monitoring
system watch the transaction age of my databases to be alerted before
we get into problems
wrapparound freeze problem indeed occur earlier? And
if so, could someone suggest a better query to monitor?
Kind Regards,
Jan Keirse
--
DISCLAIMER
http://www.tvh.com/glob/en/email-disclaimer
This message is delivered to all addressees subject to the conditions
set forth