On 09/19/2012 01:48 PM, l...@tom.com wrote:
The following bug has been logged on the website:
Bug reference: 7556
Logged by: lt
Email address: l...@tom.com
PostgreSQL version: 9.2.0
Operating system: windows xp
Description:
create table sli_test (id int primary key,info v
On 09/19/2012 09:21 PM, pathak.anu...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 7558
Logged by: Anurag
Email address: pathak.anu...@gmail.com
PostgreSQL version: 8.4.13
Operating system: Microsoft 2008 Server
Description:
Hello,
I in
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
When initially starting up, syslogger keeps stdout and stderr open
instead of closing them and reopening them from /dev/null for
proper daemonisation.
How exactly could it "close and reopen" them without losing their
ide
zim...@gmail.com writes:
> After upgrading from 9.1 to 9.2 I noticed that behaviour of veryfying table
> permissions during transaction has changed, and may be just wrong.
Fixed (or at least restored to the historical behavior). Thanks for the
report!
regards, tom lane
wrote:
> test=# explain select max(a.info)from sli_test a where a.id not
> in(select b.id from sli_test2 b where b.id<5);
> Aggregate (cost=9241443774.00..9241443774.01 rows=1 width=12)
A slower plan for NOT IN than NOT EXISTS is a fact, but definitely
not a bug. According to the stan
reinh...@m4x.de writes:
> When initially starting up, syslogger keeps stdout and stderr open instead
> of closing them and reopening them from /dev/null for proper daemonisation.
How exactly could it "close and reopen" them without losing their
identity? And what makes /dev/null necessarily the r
The following bug has been logged on the website:
Bug reference: 7559
Logged by: Reinhard Max
Email address: reinh...@m4x.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
When initially starting up, syslogger keeps stdout and stderr open instead
of
The following bug has been logged on the website:
Bug reference: 7557
Logged by: Piotr Czachur
Email address: zim...@gmail.com
PostgreSQL version: 9.2.0
Operating system: Ubuntu 12.04.1 LTS
Description:
After upgrading from 9.1 to 9.2 I noticed that behaviour of veryf
The following bug has been logged on the website:
Bug reference: 7558
Logged by: Anurag
Email address: pathak.anu...@gmail.com
PostgreSQL version: 8.4.13
Operating system: Microsoft 2008 Server
Description:
Hello,
I installed Postgres and tried by populating SHP file
The following bug has been logged on the website:
Bug reference: 7560
Logged by: Kamil Kamiński
Email address: ka...@mrblur.net
PostgreSQL version: 9.2.0
Operating system: Windows
Description:
When openssl is built on Windows it hardcodes OPENSSLDIR into its sources.
The following bug has been logged on the website:
Bug reference: 7556
Logged by: lt
Email address: l...@tom.com
PostgreSQL version: 9.2.0
Operating system: windows xp
Description:
test=# create table sli_test (id int primary key,info varchar(20));
test=# insert into s
The following bug has been logged on the website:
Bug reference: 7561
Logged by: Reinhard Max
Email address: m...@suse.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
When initially starting up, syslogger keeps stdout and stderr open instead
of cl
On Wed, Sep 19, 2012 at 6:56 PM, Andres Freund wrote:
> You see buffer pin errors or you see the relation errors? Those arent the
> same.
> So if you see no buffer pin errors but relation lock ones in production your
> way to reproduce the issue isn't telling us very much ;)
On production I hav
On Wednesday, September 19, 2012 11:33:29 AM Stuart Bishop wrote:
> On Wed, Sep 19, 2012 at 3:38 PM, Andres Freund
wrote:
> >> >> ERROR: canceling statement due to conflict with recovery
> >> >> DETAIL: User was holding shared buffer pin for too long.
> >> >
> >> > Maybe I'm missing something,
On Wed, Sep 19, 2012 at 3:38 PM, Andres Freund wrote:
>> >> ERROR: canceling statement due to conflict with recovery
>> >> DETAIL: User was holding shared buffer pin for too long.
>> > Maybe I'm missing something, but ISTM that hot_standby_feedback doesn't
>> > eliminate the query cancels cause
On Wednesday, September 19, 2012 10:06:03 AM Stuart Bishop wrote:
> On Wed, Sep 19, 2012 at 5:45 AM, Fujii Masao wrote:
> > On Mon, Sep 17, 2012 at 7:28 PM, wrote:
> >> The following bug has been logged on the website:
> >>
> >> Bug reference: 7546
> >> Logged by: Stuart Bishop
>
On Wed, Sep 19, 2012 at 5:45 AM, Fujii Masao wrote:
> On Mon, Sep 17, 2012 at 7:28 PM, wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 7546
>> Logged by: Stuart Bishop
>> Email address: stu...@stuartbishop.net
>> PostgreSQL version: 9.1.5
>> Op
17 matches
Mail list logo
