On Fri, Jul 1, 2016 at 5:49 AM, David G. Johnston
wrote:
>
> I have to agree. At worse this is a documentation bug but I do think we
> have an actual oversight here - although probably not exactly this or the
> linked bug report.
>
> Testing this out a bit on 9.5 Ubuntu 14.04 - I believe the last
On Thu, Aug 20, 2015 at 12:55 AM, Karthik Viswanathan
wrote:
> Hello,
>
> I have a master slave (read replica) setup running pg 9.4.4. I'm
> trying to find the dead tuples out both the master and slave
>
> Here's what it looks like on master:
>
> # select relname ,n_live_tup ,n_dead_tup from pg_st
On Wed, Jul 29, 2015 at 3:46 PM, Torsten Förtsch
wrote:
> Hi,
>
> we have a complex structure of streaming replication (PG 9.3) like:
>
> master --> replica1
>|
>+-> replica2 --> replica21
>|
>+--> replica22 --> replica221
>
> Now I want to retire ma
On Fri, Mar 20, 2015 at 5:54 AM, Peter Geoghegan
wrote:
> On Wed, Mar 18, 2015 at 11:03 PM, Haribabu Kommi
> wrote:
>> For our next set of development activities in PostgreSQL, we want to
>> use the Unicode organization code with PostgreSQL to open source that
>> feature
Hi All,
For our next set of development activities in PostgreSQL, we want to
use the Unicode organization code with PostgreSQL to open source that
feature. Is the Unicode license is compatible with PostgreSQL.
The following is the header that is present in one of the Unicode files.
/*
* Copyrig
On Fri, Apr 11, 2014 at 8:15 AM, CS_DBA wrote:
> Hi All;
>
> We're setting up a HOT standby on Windows 2000 server and PostgreSQL 9.2
>
> We do this:
> I've also tried this approach:
>
>
> 1) Master postgresql.conf file
> Modify the following settings:
> listen_address = '*'
> wal_level = hot_stan
On Thu, Mar 20, 2014 at 11:27 PM, Granthana Biswas wrote:
> Hello All,
>
> Has anyone ever faced the issue of dead rows not getting removed during
> vacuum even if there are no open transactions/connections?
>
> We have been facing this during every scheduled vacuum which is done after
> closing a
On Tue, Mar 11, 2014 at 7:07 AM, Aggarwal, Ajay wrote:
> Thanks Hari Babu.
>
> I think what is happening is that my dirty cache builds up quickly for the
> volume where I am backing up. This would trigger flush of these dirty pages
> to the disk. While this flush is going on pg_basebackup tries to
On Mon, Mar 10, 2014 at 12:52 PM, Aggarwal, Ajay wrote:
> Our environment: Postgres version 9.2.2 running on CentOS 6.4
>
> Our backups using pg_basebackup are frequently failing with following error
>
> "pg_basebackup: could not send feedback packet: server closed the connection
> unexpectedly
On Sat, Feb 22, 2014 at 1:21 PM, Torsten Förtsch
wrote:
> On 21/02/14 09:17, Torsten Förtsch wrote:
> > one of our streaming replicas died with
> >
> > 2014-02-21 05:17:10 UTC PANIC: heap2_redo: unknown op code 32
> > 2014-02-21 05:17:10 UTC CONTEXT: xlog redo UNKNOWN
> > 2014-02-21 05:17:11 UTC
On Mon, Feb 17, 2014 at 2:33 PM, Gabriel Sánchez Martínez <
gabrielesanc...@gmail.com> wrote:
> Is there a way of asking PostgreSQL to read the files of a table directly
> off the disk, asking the OS not to use the file cache? I am running
> PostgreSQL 9.1 on Ubuntu Server 64-bit. The server in
On Mon, Feb 17, 2014 at 7:02 PM, Jürgen Fuchsberger <
juergen.fuchsber...@uni-graz.at> wrote:
> Hi all,
>
> I have a master-slave configuration running the master with WAL
> archiving enabled and the slave in recovery mode reading back the WAL
> files from the master ("Log-shipping standby" as des
On Sun, Feb 16, 2014 at 9:38 PM, Rémi Cura wrote:
> Hey Dear List,
> could somebody point me to some ressources about getting only parts of
> toasted data?
>
> I have a very big custom type and I would like to take blocks of it (like
> byte A to B then byte C to D then... ).
>
> I found a functi
On 30 December 2013 19:11 Leonardo M. Ramé wrote:
> Hi, I want know if I should run the auto-vacuum daemon (from
> /etc/init.d/) or it runs automatically and transparently if configured
> in postgres.conf?. If it must be configured manually, what is the
> script to be run, I didn't find pg_autovacu
On 12 November 2013 07:49 Maxim Boguk wrote:
>Hi everyone,
>
>I have few question about checkpoints during create database.
>
>First just extract from log on my test database 9.2.4:
>
>2013-11-12 03:48:31 MSK 1717 @ from [vxid: txid:0] [] LOG: checkpoint
>starting: immediate force wait
>2013-11-
On 05 September 2013 18:50 ascot.moss wrote:
>From the pg_xlog folder, I found some files with interesting time stamps:
>older file names with newer timestamps, can you please advise why?
>Set 1: How come 00040F49008D is 10 minutes newer than
>00040F49008E?
>-rw--- 1
On 06 August 2013 16:13 ascot.moss wrote
>Hi,
>I just setup the replication in the slave again, when trying to use psql, I
>could not get the psql command prompt but got "psql: FATAL: the database
>system is starting up" from it.
>PG: 9.2.4
>Below is the log from the the slave:
>LOG: datab
17 matches
Mail list logo
