Re: [GENERAL] Referential integrity question

2000-11-05 Thread William H. Geiger III
In <[EMAIL PROTECTED]>, on 11/05/00 at 10:12 AM, "Raymond O'Donnell" <[EMAIL PROTECTED]> said: >Hi all, >Is this normal? - I have discovered the hard way that permissions >GRANTed to a user on one table influence that user's ability to update >another table in a foreign key relationship wi

Re: [GENERAL] where to find postgresql jobs in the Washington, DCarea??

2000-11-05 Thread John McKown
I totally agree that putting job postings here would be undesirable. Well, at least for me. I don't want a job, I've got one. However, the addition of a job mailing list by itself would be OK by me. But I wonder how effective it would be. I guess if the list is archived, then that would be a bit b

[GENERAL] PG and login

2000-11-05 Thread Jarmo Paavilainen
Hi, Where does the backend do its user validation? If I login with "psql -u" how does the backend take care of the username and password? Ive tried to find where it happens without success (using a lot of elog(DEBUG,...)). (we are talking "password" identification, not "ident", kerberos or "cry

[GENERAL] Expectations of MEM requirements for a DB with large tables.

2000-11-05 Thread Michael Miyabara-McCaskey
Hello to all, I am new to the PostgreSQL world, as well as the Linux world... kind of a double whammy... Anyway, I crashed my system the other day when I did a "select *" from one of my large tables (about 5.5gb in size). Now this is not something that will normally happen, as I would normally h

Re: [GENERAL] Expectations of MEM requirements for a DB with large tables.

2000-11-05 Thread Bruce Guenter
On Sun, Nov 05, 2000 at 09:17:52PM -0800, Michael Miyabara-McCaskey wrote: > Anyway, I crashed my system the other day when I did a "select *" from one > of my large tables (about 5.5gb in size). Now this is not something that > will normally happen, as I would normally have some criteria to reduc

Re: [GENERAL] Expectations of MEM requirements for a DB with large tables.

2000-11-05 Thread KuroiNeko
Mike, > Anyway, I crashed my system the other day when I did a "select *" from > one > of my large tables (about 5.5gb in size). Well It takes abit more than that to actually crash the system. Can you give more details? What _exactly_ happened? Did it hang? Kernel panicked?

RE: [GENERAL] Expectations of MEM requirements for a DB with large tables.

2000-11-05 Thread Michael Miyabara-McCaskey
Bruce, Your assumptions were absolutely on target. I appreciate the fact that you de-coupled my question as well. As I was in fact using "psql", this certainly explains my system dropping to it's knees... Out of curiosity, if I were using something else besides "psql" would this have still bee

RE: [GENERAL] Expectations of MEM requirements for a DB with large tables.

2000-11-05 Thread Michael Miyabara-McCaskey
Kuroi, Thank you for the response. I was not specifically thinking of diagnosing my crash, but if you are curious... - about a 1000 error messgaes saying that kswapd could not do something relating to allocating memory. - after stopping the "psql" job, it still took about 20 minutes before m