Darek Czarkowski <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> BTW, I checked the CVS logs, and AFAICT this entry refers to the bug
>> and patch shown in this thread:
>> http://archives.postgresql.org/pgsql-general/2003-10/msg00888.php
>> I'd be interested to know how your application is dependi
Tom Lane wrote:
Darek Czarkowski <[EMAIL PROTECTED]> writes:
I am sorry, it seams that my last replay never reached the list.
I was looking for the list of changes for each version, but this document i=
s bundled with the source. I believe it is the fix introduced in version 7.=
3.5:
"* Fix i
Darek Czarkowski <[EMAIL PROTECTED]> writes:
> I am sorry, it seams that my last replay never reached the list.
> I was looking for the list of changes for each version, but this document i=
> s bundled with the source. I believe it is the fix introduced in version 7.=
> 3.5:
> "* Fix insertion of
I am sorry, it seams that my last replay never reached the list.
I was looking for the list of changes for each version, but this document is
bundled with the source. I believe it is the fix introduced in version 7.3.5:
"* Fix insertion of expressions containing subqueries into rule bodies"
Above
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> On 9/6/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> What changes would those be? If your app works on 7.3.4 it should work
>> with 7.3.17.
> Actually, from what he wrote, I take it that 7.3.17 works fine, but
> some insane policy where he works demands
On 9/6/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Darek Czarkowski <[EMAIL PROTECTED]> writes:
> > It can not be the resource limit, it has to be something else. I assume thi=
> > s version of postgres is incompatible with RedHat ES 5. Changing to a newer=
> > version of postgres is not an option f
Darek Czarkowski <[EMAIL PROTECTED]> writes:
> It can not be the resource limit, it has to be something else. I assume thi=
> s version of postgres is incompatible with RedHat ES 5. Changing to a newer=
> version of postgres is not an option for now. It would take too much time =
> to rewrite the
Thank you for comments, did I mention the system is a beast?
# cat /proc/sys/kernel/shmmax
68719476736
It can not be the resource limit, it has to be something else. I assume this
version of postgres is incompatible with RedHat ES 5. Changing to a newer
version of postgres is not an option for
Darek Czarkowski <[EMAIL PROTECTED]> writes:
> I am have installed postgresql-7.3.4 on Linux server running Red Hat Enterp=
> rise Linux Server release 5 (Tikanga).
Why in heavens name would you be wanting to run 7.3.4? Even if you have
a good reason for wanting 7.3.x, you should be installing 7.
Hi,
On Fri, 2007-08-31 at 18:11 -0700, Darek Czarkowski wrote:
> when I try to increase number of connections to 200 I get
> "IpcSemaphoreCreate: semget(key=5432120, num=17, 03600) failed: No
> space left on device" Error
>
> Now, I dont think the default system settings are too low, default
> s
Hello,
I am have installed postgresql-7.3.4 on Linux server running Red Hat Enterprise
Linux Server release 5 (Tikanga).
Postmaster runs fine with the default settings, but when I try to increase
number of connections to 200 I get
"IpcSemaphoreCreate: semget(key=5432120, num=17, 03600) failed:
11 matches
Mail list logo
