On Mon, Oct 8, 2012 at 10:42 AM, Amit Kapila wrote:
> How about following:
> 1. replication_client_timeout -- shouldn't it be client as new configuration
> is for wal receiver
> 2. replication_standby_timeout
ISTM that the client and the standby are the same thing.
> If we introduce a new parame
The following bug has been logged on the website:
Bug reference: 7591
Logged by: Pat King
Email address: pk...@nrcan.gc.ca
PostgreSQL version: 9.1.3
Operating system: RedHat Linux 6.2
Description:
Hi :
I am dealing with the open source program called "Geonetwork". It
The following bug has been logged on the website:
Bug reference: 7590
Logged by: Jan Vodička
Email address: hrt...@gmail.com
PostgreSQL version: 9.2.1
Operating system: Windows 8
Description:
"pg_dump -Z1 my_db > backup" always make corrupted package.
When I try it on
serovov+pg...@gmail.com writes:
> 01=# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id);
> ERROR: canceling statement due to statement timeout
> 01=# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id);
> ERROR: relation "obj_pkey" already exists
This is not a bug, it is the documented fa
On Tuesday, October 09, 2012 6:00 PM Robert Haas wrote:
> On Mon, Oct 8, 2012 at 10:42 AM, Amit Kapila
> wrote:
> > How about following:
> > 1. replication_client_timeout -- shouldn't it be client as new
> configuration
> > is for wal receiver
> > 2. replication_standby_timeout
>
> ISTM that the
pk...@nrcan.gc.ca writes:
> I am dealing with the open source program called "Geonetwork". It is passing
> the following query to postgres/postgis :
> SELECT "fid", asText("the_geom") FROM "public"."spatialindex" WHERE ("fid" =
> '10') OR ("fid" = '100') OR ("fid" = '1000') OR ("fid" = '10001') O
The following bug has been logged on the website:
Bug reference: 7589
Logged by: Oleg
Email address: serovov+pg...@gmail.com
PostgreSQL version: 9.1.6
Operating system: CentOs
Description:
See sql console:
01=# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id);
hrt...@gmail.com writes:
> The following bug has been logged on the website:
> Bug reference: 7590
> Logged by: Jan VodiÄka
> Email address: hrt...@gmail.com
> PostgreSQL version: 9.2.1
> Operating system: Windows 8
> Description:
> "pg_dump -Z1 my_db > backup" always
On Tue, Oct 09, 2012 at 02:20:40PM +, hrt...@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7590
> Logged by: Jan Vodička
> Email address: hrt...@gmail.com
> PostgreSQL version: 9.2.1
> Operating system: Windows 8
> Description:
So is there any way how to get plain sql from this "corrupted" backup?
It would be nice to mention this behavior in manual.
2012/10/9 Tom Lane
> hrt...@gmail.com writes:
> > The following bug has been logged on the website:
> > Bug reference: 7590
> > Logged by: Jan Vodička
> > Em
= not able to unpack, invalid
Try this one generated by "pg_dump -Z1 > backup.gz" in windows:
http://mstu.cz/~hrtlik/backup.gz (0.5kB)
original "pg_dump > backup.gz" without compression:
http://mstu.cz/~hrtlik/backup.sql
If you have any way how to get original, tell me.
2012/10/9 Ryan Kelly
11 matches
Mail list logo
