OK, there is a patch on the patches web archive around May 5 for
Kerberos. If it solves your problems, please let me know and I will
have the new code in 7.0.1. Please report back. Thanks.
Attempting my first kerberos'd install of postgresql and am finding
errors. Being new to kerberos
I know that there were some issues with many AND/OR joins in PostgreSQL 6.5
which caused the backend process to run out of memory. I am still having
some similar issues in PostgreSQL 7.0. I was wondering if there some
recommended configurations (i.e. amount of RAM on the machine, size of swap
[postgres@warpfactor2 pgsql]$ ulimit -a
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes)unlimited
open files 1024
pipe size (512 bytes) 8
stack size
tables are not that large...
essentially we are working on a tool for someone to be able to slice and
dice their database any which way they
want. Thus it allows users to create really ugly SQL with a bunch of AND/OR
joins. I am currently running on
a box with 128M. I have tried ulimit -s
Bruce Momjian [EMAIL PROTECTED] writes:
stack size (kbytes) 8192
I bet this is the problem.
Nah, 8 meg stack should be fine --- that's the same configuration I run.
On Thu, 11 May 2000, Gregory Krasnow wrote:
I know that there were some issues
At 07:21 PM 11-05-2000 -0300, The Hermit Hacker wrote:
Do you not have a copy of the code sitting in front of you, or
nearby? Don't greater then, oh, 50 mirror sites? Don't 500 downloads of
v7.0 since release? My point is that nobody can ever 'take PostgresQL
proprietary' ... the best they
