[GENERAL] semaphore not equal 0

2000-04-22 Thread Joseph
I get the following error running postgress 6.5.3 on win32. What might I be doing wrong? It runs and works but it says the following many times. Error semaphore semaphore not equal 0 Joseph

[GENERAL] too many clients - Error message

2000-04-22 Thread Joseph
How do you solve this error message? Connection to database 'template1' failed. Sorry, too many clients already Joseph

[GENERAL] unique row identifier data type exhausted . . .

2000-04-22 Thread Frank Joerdens
It feels like there should be some *really* obvious answer to this question, and I'll find myself whacking my forehead in self-abasement and out of sheer relief to have found the answer to a problem that should not have bothered me in the first place since the answer is too self-evident . . . howe

Re: [GENERAL] too many clients - Error message

2000-04-22 Thread Charles Tassell
The maximum number of backends that the PostGres postmaster will start is 32. If you want more, you have to specify the maximum on the command line with the -N option. IE, you can start postgres like this to allow internet connections, have it fork into the background, and allow 100 simultaneo

[GENERAL] Where can I get free ODBC drivers for postgres?

2000-04-22 Thread SUDDN
Are there any free ODBC drivers avaliable? If so where can I find them? Thanks

[GENERAL] storing large amounts of text

2000-04-22 Thread Paul Dlug
I'm sure this has come up before because it just logically seems like others would have run up against this too. Is it possible to store a large amount of text in a row/field? I want to store articles in the database along with information about them, sort of a content databasing system. Can anyon

Re: [GENERAL] storing large amounts of text

2000-04-22 Thread Stephan Richter
At 08:19 PM 4/22/00 +, Paul Dlug wrote: >I'm sure this has come up before because it just logically seems like >others would have run up against this too. Is it possible to store a >large amount of text in a row/field? I want to store articles in the >database along with information about them

Re: [GENERAL] storing large amounts of text

2000-04-22 Thread Paul Dlug
I thought TEXT had a limit of 8K or something around that size, I would need something larger. Stephan Richter wrote: > > At 08:19 PM 4/22/00 +, Paul Dlug wrote: > >I'm sure this has come up before because it just logically seems like > >others would have run up against this too. Is it possi

Re: [GENERAL] storing large amounts of text

2000-04-22 Thread Titus Brown
-> I'm sure this has come up before because it just logically seems like -> others would have run up against this too. Is it possible to store a -> large amount of text in a row/field? I want to store articles in the -> database along with information about them, sort of a content databasing -> sy

Re: [GENERAL] storing large amounts of text

2000-04-22 Thread Brett W. McCoy
On Sat, 22 Apr 2000, Paul Dlug wrote: > I thought TEXT had a limit of 8K or something around that size, I would > need something larger. You'd be better off breaking the text up into smaller fields. Another option is to store a pathname to a file that contains the text of your article. Brett W

RE: [GENERAL] unique row identifier data type exhausted . . .

2000-04-22 Thread Andrew Snow
> It feels like there should be some *really* obvious answer to this > question, and I'll find myself whacking my forehead in self-abasement > and out of sheer relief to have found the answer to a problem that > should not have bothered me in the first place since the answer is too > self-evident

[GENERAL] Large objects...

2000-04-22 Thread Andrew Schmeder
Hello all, I am attempting to use large objects to store chunks of text and binary data. I am using PHP and sometimes need to do things through psql also. PHP has a function to "unlink" a large object, i.e. delete it. Is there an explict way to delete a large object via psql? I have been using

Re: [GENERAL] unique row identifier data type exhausted . . .

2000-04-22 Thread Jurgen Defurne
Frank Joerdens wrote: > It feels like there should be some *really* obvious answer to this > question, and I'll find myself whacking my forehead in self-abasement > and out of sheer relief to have found the answer to a problem that > should not have bothered me in the first place since the answer