On 15.02.2012 07:09, Andy Grimm wrote:
Sorry that it's been a couple of weeks, but I have gotten around to
working on a patch that address more of these concerns. The attached
patch should
1) allow arbitrary length passwords to be read from a file via initdb --pwfile
2) allow the client to acce
On 20.09.2012 00:05, Reinhard Max wrote:
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
And what makes /dev/null necessarily the right substitute?
Because it is what virtually all deamons have been doing for the last
3..4 decades?
I don't think we should change this wi
On 09/20/2012 01:14 PM, l...@tom.com wrote:
> plan of http://archives.postgresql.org/pgsql-bugs/2012-09/msg00222.php
> 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);
>QUERY PLAN
>
On Thu, 20 Sep 2012 at 10:31, Heikki Linnakangas wrote:
I believe Tom is referring to the removal of silent_mode in 9.2, see
http://archives.postgresql.org/pgsql-general/2011-06/msg00796.php
and
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02156.php.
"We removed logic associated w
plan of http://archives.postgresql.org/pgsql-bugs/2012-09/msg00222.php
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);
QUERY PLAN
---
Reinhard Max writes:
> After starting PostgreSQL with pg_init, stdout and stderr of all
> processes are pipes to the logger (as intended), but the logger itself
> still has FDs 1 and 2 open as inherited from pg_init. I think
> requiring the caller of pg_init to redirect them is not practical,
The following bug has been logged on the website:
Bug reference: 7562
Logged by: Mayank Mittal
Email address: mayank.mittal.1...@hotmail.com
PostgreSQL version: 9.1.5
Operating system: Debian Linux 6.0
Description:
We are using 2 node set-up of PostgreSQL 9.1.5 in whi
Reinhard Max writes:
> On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
>> Well, I would have no objection to changing pg_ctl so that it
>> redirects the postmaster's stdout/stderr when a -l switch is given
>> (actually, I thought it did that already...).
> Well, going that route forces me to eith
mayank.mittal.1...@hotmail.com writes:
> The following bug has been logged on the website:
> Bug reference: 7562
> Logged by: Mayank Mittal
> Email address: mayank.mittal.1...@hotmail.com
> PostgreSQL version: 9.1.5
> Operating system: Debian Linux 6.0
> Description:
>
Hello Tom, Thanks for the information. But problem is it is occurring quite
frequently in my case.
Regards,
Mayank Mittal
> From: t...@sss.pgh.pa.us
> To: mayank.mittal.1...@hotmail.com
> CC: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #7562: could not read block 0 in file
> "base/16
On Thursday, September 20, 2012 07:15:17 PM Tom Lane wrote:
> mayank.mittal.1...@hotmail.com writes:
> > The following bug has been logged on the website:
> > Bug reference: 7562
> > Logged by: Mayank Mittal
> > Email address: mayank.mittal.1...@hotmail.com
> > PostgreSQL version
Andres Freund writes:
> On Thursday, September 20, 2012 07:15:17 PM Tom Lane wrote:
>> Hmm. There is a fix for a slave-side-index-corruption problem in 9.1.6,
>> which is due to be announced Monday. I am not certain whether this is
>> the same thing though; that bug is low-probability as far as
On Thursday, September 20, 2012 11:38:52 PM Tom Lane wrote:
> Andres Freund writes:
> > On Thursday, September 20, 2012 07:15:17 PM Tom Lane wrote:
> >> Hmm. There is a fix for a slave-side-index-corruption problem in 9.1.6,
> >> which is due to be announced Monday. I am not certain whether this
Andres Freund writes:
> On Thursday, September 20, 2012 11:38:52 PM Tom Lane wrote:
>> Sure, but what about the heap? The case I was speculating about was
>> that the heap had been truncated, but because of the corruption problem,
>> the index still had heap pointers in it. We don't know what fi
On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
(I assume you mean pg_ctl not pg_init?)
Yes, sorry for the confusion.
Well, I would have no objection to changing pg_ctl so that it
redirects the postmaster's stdout/stderr when a -l switch is given
(actually, I thought it did that already...).
Here is a snapshot of installed postgresql packages:
mayank@server:~$ dpkg -l | grep postgres
ii
postgresql-9.1
9.1.5-1~bpo60+1
object-relational SQL database, version 9.1 server
ii
postgresql-client-9.1
9.1.5-1~bpo60+1
front-end prog
16 matches
Mail list logo
