bOn 06/17/2011 04:47 PM, Антон Степаненко wrote:
Memory for shared buffers can not be ovesubscribed - because if kernel
did not provide enough shared memory postgres will not start.
The block is allocated at once. But the amount of it that various
client backends end up touching varies as the
On Fri, 17 Jun 2011 19:51:59 +0200, Tom Lane wrote:
I looked at the glibc source code for getaddrinfo, and it looks like
they do reliably set sin_port to zero when no service argument is
provided, despite the above documentation statement. So that's why it
works for me. But still, if you're o
2011/6/17 Антон Степаненко :
>>
>> I wonder if you are oversubscribing your memory, and are getting weird
>> errors when reading data into memory because the pages can't be
>> reserved to do that. What happens when you enable overcommit and
>> attempt to start the server?
>>
>> merlin
>
> In my fi
>
> I wonder if you are oversubscribing your memory, and are getting weird
> errors when reading data into memory because the pages can't be
> reserved to do that. What happens when you enable overcommit and
> attempt to start the server?
>
> merlin
In my first post I wrote: "I tried to set vm.ov
2011/6/17 Антон Степаненко :
> 17.06.2011, 21:24, "Merlin Moncure" :
>> 2011/6/17 Антон Степаненко ;:
>>
>>> 17.06.2011, 20:19, "Merlin Moncure" ;:
On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
;; wrote:
>> I still do not believe that this is hardware problem.
> How woul
17.06.2011, 21:24, "Merlin Moncure" :
> 2011/6/17 Антон Степаненко ;:
>
>> 17.06.2011, 20:19, "Merlin Moncure" ;:
>>> On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
>>> ;; wrote:
> I still do not believe that this is hardware problem.
How would an application cause a bus error?
2011/6/16 Luiz K. Matsumura :
> Em 16/06/2011 16:39, Robert Haas escreveu:
>
> 2011/6/10 Luiz K. Matsumura :
>
> I need help to know if the follow scenario is a expected behaviour, a bug of
> postgres or a bug of slony:
>
> Postgres v8.4.8
> Slony-I v 2.0.5
>
> I have table replicated with slony an
I wrote:
> I don't think it's a race condition per se. The code ought to be
> setting up the address argument for bind() with sin_port = 0 so that
> an unused port number gets assigned. That seems to be what happens on
> a couple of machines that I tried here, but I notice that the Linux
> manpag
2011/6/17 Антон Степаненко :
>
>
> 17.06.2011, 20:19, "Merlin Moncure" :
>> On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
>> ; wrote:
>>
I still do not believe that this is hardware problem.
>>> How would an application cause a bus error?
>>
>> unaligned memory access on risc maybe? what
17.06.2011, 20:19, "Merlin Moncure" :
> On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
> ; wrote:
>
>>> I still do not believe that this is hardware problem.
>> How would an application cause a bus error?
>
> unaligned memory access on risc maybe? what's this running on?
>
> merlin
*:~$
On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
wrote:
>> I still do not believe that this is hardware problem.
>
> How would an application cause a bus error?
unaligned memory access on risc maybe? what's this running on?
merlin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
* ** wrote:
> 17.06.2011, 00:28, "Kevin Grittner" :
>> * **; wrote:
>>
>>> [4-1] 2011-06-16 17:40:27 UTC LOG: startup process (PID 15292)
>>> was terminated by signal 7: Bus error
>>> Signal 7 means hardware problems. But all 10 replicas crashed
>>> within 10 minutes,
"Marinos Yannikos" writes:
> I'm not sure that this is not a configuration or networking issue (so
> apologies if it is), but we seem to be getting rare (a few times/day)
> failures with ident authentication because several clients attempt to do
> it simultaneously over a high-latency connec
"Ben" writes:
> Operating system: üLinux version 2.6.21-uc0 on ARM processor
> (NXP-LPC2478)
> Description:FATAL: lock 0 not held
> Details:
> while initialising with initdb, after creating and filling new WAL file.
> We see LWLockAcquire(11) followed by LWLockRelease(0) and then a FA
Excerpts from Christoph Berg's message of vie jun 17 07:10:34 -0400 2011:
> Re: To pgsql-bugs@postgresql.org 2011-06-17
> <20110617091114.gc4...@msgid.df7cb.de>
> > Unfortunately that doesn't help in this case, as the bad string isn't
> > tagged as "#, c-format", but still gets used as such. This
"Michael Pilling" wrote:
> A reasonable programmer would expect != NULL, <> NULL and IS NOT
> NULL to be synonyms.
Only if that programmer was not aware of the SQL standard and had
not worked much with a standard-conforming database.
NULL is conceptually intended to indicate "unknown" or "no
17.06.2011, 00:28, "Kevin Grittner" :
> * **; wrote:
>
>> [4-1] 2011-06-16 17:40:27 UTC LOG: startup process (PID 15292)
>> was terminated by signal 7: Bus error
>> Signal 7 means hardware problems. But all 10 replicas crashed
>> within 10 minutes, say from 13:35 to 13:45.
>> O
The following bug has been logged online:
Bug reference: 6065
Logged by: Ben
Email address: bwtes...@yahoo.com
PostgreSQL version: 9.0.4
Operating system: üLinux version 2.6.21-uc0 on ARM processor
(NXP-LPC2478)
Description:FATAL: lock 0 not held
Details:
while init
Re: To pgsql-bugs@postgresql.org 2011-06-17
<20110617091114.gc4...@msgid.df7cb.de>
> Unfortunately that doesn't help in this case, as the bad string isn't
> tagged as "#, c-format", but still gets used as such. This seems to be
> the case for many errhint() strings. Maybe xgettext should be taught
Hi,
I'm not sure that this is not a configuration or networking issue (so
apologies if it is), but we seem to be getting rare (a few times/day)
failures with ident authentication because several clients attempt to do
it simultaneously over a high-latency connection (capitalized = edited
I
Re: Heikki Linnakangas 2011-06-17 <4dfb137e.4040...@enterprisedb.com>
> So, this is a case where the untranslated string doesn't have a %s
> in it, but the translated one does. We should have a way to check
> those automatically. In fact, I'm surprised if someone somewhere
> hasn't already written
On 17.06.2011 11:22, Bernd Helmle wrote:
--On 17. Juni 2011 08:18:03 + Christoph Berg wrote:
In German locale, the follow statement causes vsnprintf() to segfault
when
printing the hint:
SELECT TO_DATE('30.12.2011', 'MMDD') AS datum;
Fix tested for 8.4:
Additionally, this seems to
--On 17. Juni 2011 08:18:03 + Christoph Berg wrote:
In German locale, the follow statement causes vsnprintf() to segfault when
printing the hint:
SELECT TO_DATE('30.12.2011', 'MMDD') AS datum;
Fix tested for 8.4:
Additionally, this seems to be the case for 9.0, 9.1 and current -HE
The following bug has been logged online:
Bug reference: 6066
Logged by: Christoph Berg
Email address: c...@df7cb.de
PostgreSQL version: 9.1, 9.0, 8.4
Operating system: any
Description:Bad string in German translation causes segfault
(user-triggerable)
Details:
In G
Do not write expression = NULL because NULL is not "equal to" NULL. (The
null value represents an unknown value, and it is not known whether two
unknown values are equal.) This behavior conforms to the SQL standard.
http://www.postgresql.org/docs/9.1/static/functions-comparison.html
On Fri, Jun
The following bug has been logged online:
Bug reference: 6064
Logged by: Michael Pilling
Email address: michael.pill...@dsto.defence.gov.au
PostgreSQL version: PostgreSQL 9.0
Operating system: Windows XP (server) Ubuntu 10.4 (Client)
Description:!= NULL, <> NULL do no
26 matches
Mail list logo
