The following bug has been logged on the website:
Bug reference: 7596
Logged by: David PEYRIERES
Email address: david.peyrie...@meteo.fr
PostgreSQL version: 9.1.4
Operating system: Red Hat
Description:
Hello.
I found a little bug in /etc/init.d/postgresql-9.x file (ok
On Thu, Oct 11, 2012 at 2:59 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7596
> Logged by: David PEYRIERES
> Email address: david.peyrie...@meteo.fr
> PostgreSQL version: 9.1.4
> Operating system: Red Hat
> Description:
>
Hi David,
How d
The following bug has been logged on the website:
Bug reference: 7597
Logged by: Bo T Jensen
Email address: b...@budget123.dk
PostgreSQL version: 9.1.6
Operating system: windows 7 home premium 64
Description:
Ive managed to boil this down to a repeatable example on a
Self-contained case attached.
crash2.sql
Description: crash2.sql
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wednesday, October 10, 2012 9:15 PM Heikki Linnakangas wrote:
> On 04.10.2012 13:12, Amit kapila wrote:
> > Following changes are done to support replication timeout in sender as
> well as receiver:
> >
> > 1. One new configuration parameter wal_receiver_timeout is added to
> detect timeout at
On 10/11/2012 06:07 PM, Bo Thorbjørn Jensen wrote:
Self-contained case attached.
No crash here on version() = PostgreSQL 9.1.5 on
x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.7.0 20120507 (Red Hat
4.7.0-5), 64-bit
On 11.10.2012 14:42, Craig Ringer wrote:
On 10/11/2012 06:07 PM, Bo Thorbjørn Jensen wrote:
Self-contained case attached.
No crash here on version() = PostgreSQL 9.1.5 on
x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.7.0 20120507 (Red Hat
4.7.0-5), 64-bit
I can reproduce this on my Window
Heikki Linnakangas writes:
> On 11.10.2012 14:42, Craig Ringer wrote:
>> No crash here on version() = PostgreSQL 9.1.5 on
>> x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.7.0 20120507 (Red Hat
>> 4.7.0-5), 64-bit
> I can reproduce this on my Windows box with the script Bo provided, with
> a f
On 11.10.2012 13:17, Amit Kapila wrote:
How does this look now?
The Patch is fine and test results are also fine.
Ok, thanks. Committed.
- Heikki
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-b
I wrote:
> I see it too. I think the crash probably only occurs on a 32-bit build
> (or one where you've disabled int8-pass-by-value anyway). Looks like
> something's confused about cross-data-type comparisons --- this is an
> int4 vs int8 comparison, so it shouldn't be ending up at int8eq.
Argh
On Thursday, October 11, 2012 8:22 PM Heikki Linnakangas wrote:
On 11.10.2012 13:17, Amit Kapila wrote:
>>> How does this look now?
>
>> The Patch is fine and test results are also fine.
>Ok, thanks. Committed.
Thank you very much.
With Regards,
Amit Kapila.
--
Sent via pgsql-bugs mailing
The following bug has been logged on the website:
Bug reference: 7598
Logged by: Vaclav Juza
Email address: vaclav.j...@xitee.com
PostgreSQL version: 9.2.1
Operating system: Linux 2.6.18-128.el5 x86_64 (RHEL 5.3)
Description:
Hi,
when a view (with the below properites
Hi Srinivas,
The error comes becoz of two reasons.
1)U didn't create XDBSYS
2) limit_connections='*' is not given in
/usr/local/pgsql/data/postgres.conf
to create XDBSYS
createdb XDBSYS -u gridsql
./gs-createmddb.sh -u admin -p secret
Ashu.
--
View this message in conte
The following bug has been logged on the website:
Bug reference: 7595
Logged by: seowoong kim
Email address: hikkis...@hotmail.com
PostgreSQL version: 9.1.3
Operating system: windows 7 (x64)
Description:
hi
I'm using postgreSQL 9.1.3 version.
there's some problem wi
small correction in above msg
its not limit_connections='*' but
listen_addresses='*'
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-6451-problem-while-installing-gridsql-tp5469996p5727648.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
Forwarding this to pgsql-bugs, since this isn't a security issue, as
pg_ctl can only be called an admin. My replies inline.
Original Message
Subject: [pgsql-security] race in pg_ctl start -w
Date: Thu, 11 Oct 2012 12:39:02 -0400
From: Dave Vitek
To:
Hi,
I don't really thin
Heikki Linnakangas writes:
> A straightforward fix would be to just allocate one large-enough buffer
> to begin with, e.g 8k, and read the whole file in one go. I'll write up
> a patch for that.
This makes the readfile function very usage-specific though. The fix
I was thinking about was to mo
On 11.10.2012 20:29, Tom Lane wrote:
Heikki Linnakangas writes:
A straightforward fix would be to just allocate one large-enough buffer
to begin with, e.g 8k, and read the whole file in one go. I'll write up
a patch for that.
This makes the readfile function very usage-specific though. The f
Heikki Linnakangas writes:
> Hmm, starting with 9.3, postmaster can not only create and append to the
> end of file, it can also inject a line in the middle, shifting the
> following lines forwards. In theory, if a new line is injected into the
> middle of the file between fgets() calls, readfi
Hi,
with rpm.
Ashesh Vashi a écrit :
On Thu, Oct 11, 2012 at 2:59 PM, wrote:
The
following bug has been logged on the website:
Bug reference: 7596
Logged by: David PEYRIERES
Email address: david.peyrie...@meteo.fr
PostgreSQL version: 9.
On 10/11/12 2:29 AM, david.peyrie...@meteo.fr wrote:
In my case, I've 5 databases on same server. Each database is start/stop
with this file 'service postgresql9.x start'.
one database 'cluster' (instance of the postmaster, with a corresponding
$PGDATA directory) can have any number of databa
21 matches
Mail list logo