On 04/10/12 19:06, Simon Riggs wrote:
On 4 October 2012 05:32, Mark Kirkwood wrote:
I am seeing the situation where the reported flush location for the sync
standby (standby1 below) is *behind* the reported current xlog location of
the primary. This is Postgres 9.1.5 , and I was under the impre
On Tuesday, October 02, 2012 1:56 PM Heikki Linnakangas wrote:
On 02.10.2012 10:36, Amit kapila wrote:
> On Monday, October 01, 2012 4:08 PM Heikki Linnakangas wrote:
>>> So let's think how this should ideally work from a user's point of view.
>>> I think there should be just two settings: walsende
> -Original Message-
> From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-
> ow...@postgresql.org] On Behalf Of Amit kapila
> Sent: Thursday, October 04, 2012 3:43 PM
> To: Heikki Linnakangas
> Cc: Fujii Masao; pgsql-bugs@postgresql.org; pgsql-hack...@postgresql.org
> Subject: Re: [
The following bug has been logged on the website:
Bug reference: 7583
Logged by: Bryan Love
Email address: bryan.l...@iovation.com
PostgreSQL version: 9.2.1
Operating system: Centos 6
Description:
After creating a table using LIKE and INHERITS, if you drop a column fr
bryan.l...@iovation.com writes:
> After creating a table using LIKE and INHERITS, if you drop a column from
> the parent table that existed prior to creation of the child table, the
> column will not be dropped from the child table.
This is not a bug. LIKE says the column isn't inherited, so it e
On Thu, Oct 4, 2012 at 10:40:19AM +1000, Maxim Boguk wrote:
>
> > Test database have a bit unusual tablespace layout:
> > main tablespace partition was mounted inside data directory of the old
> > cluster...
> > E.g.:
> > data directory - /var/lib/postgresql/9.2/main
> > m
Understood, thanks.
Our use case is that we want to copy the indexes from the parent table as
well, so we have to use (like ... including indexes).
On Thu, Oct 4, 2012 at 7:38 AM, Tom Lane wrote:
> bryan.l...@iovation.com writes:
> > After creating a table using LIKE and INHERITS, if you drop a
