Re: [ADMIN] Yet Another Socket .s.PGSQL.5432 Problem

Am Donnerstag, 16. August 2007 23:41 schrieb Hilton Perantunes: Alvaro, it works like a charm =). Thank you all. Bad, bad Debian.. no cookies for you (and I'll read the error messages more carefully next time)! The problem is quite likely some variant on the following: You had your

[ADMIN] adding a user with the permission to create trimmed users

Hi! I want to know whether there exist the possibility to create a user who has the permission to create users with preset limited permissions. In detail: I do not want that the admin user (a seperate limited one for the customer) is able to create full admin users or adequate ones.

Re: [ADMIN] Yet Another Socket .s.PGSQL.5432 Problem

Exactly what happened, Peter. Something was preventing me of successfully install 8.2.4 through apt-get, so I did it by hand. I'll read the documentation about LD_LIBRARY_PATH. Thank you. Hilton Perantunes On 8/17/07, Peter Eisentraut [EMAIL PROTECTED] wrote: Am Donnerstag, 16. August 2007

Re: [ADMIN] adding a user with the permission to create trimmed users

On Fri, Aug 17, 2007 at 4:50 AM, in message [EMAIL PROTECTED], Peter Elmers [EMAIL PROTECTED] wrote: I want to know whether there exist the possibility to create a user who has the permission to create users with preset limited permissions. In detail: I do not want that the admin user

[ADMIN] help with query

I need a little bit of help. I need to use sql to pull any tables that have the a foreign key referencing a given tables primary key. So far I have come up with the listed query. It works great for single column primary keys, but if a table has a multi column primary key, it is returning to

[ADMIN] Cannot read block x of relation a/b/c: Invalid argument

Good afternoon all, I'm attempting to run a pg_dumpall on an existing Win2000 SP4 server (v8.1.8) before upgrading to v8.2.4 and am running into some disconcerting error messages. The first time I did a 'pg_dumpall -s -c -U postgres -W', I received the following error messages: pg_dump: SQL

Re: [ADMIN] help with query

Why not use information_schema? select prk.table_name AS PARENT_TABLE, prk.constraint_name AS PK, tc.table_name AS CHILD_TABLE, refc.constraint_name AS FK from information_schema.table_constraints prk, information_schema.referential_constraints refc,

[ADMIN] Invalid String enlargement

Hi, We are planning on upgrading to postgres 8.2.4 from 8.0, we are seeing some errors like invalid string enlargement request size 1476395004 after upgrade. Not sure what this error is about, We dont see any errors at the application side when this error occurs at the database end.

[ADMIN] compilation error on CentOS 5

Hi, I am having difficulty compiling my postgresql 7.2.3 on a CentOS 5. The same code works on our build machine which is running RedHat 7.2. I have checked many of the configure(1) output with no major diff. Capturing the output of make reveals a silly problem which I am failing to find the

Re: [ADMIN] Invalid String enlargement

Pallav Kalva [EMAIL PROTECTED] writes: We are planning on upgrading to postgres 8.2.4 from 8.0, we are seeing some errors like invalid string enlargement request size 1476395004 after upgrade. This seems like it must be a server bug, and yet this log trace: LOG: incomplete message

Re: [ADMIN] compilation error on CentOS 5

Medi Montaseri [EMAIL PROTECTED] writes: I am having difficulty compiling my postgresql 7.2.3 on a CentOS 5. Why in the world are you trying to build a five-year-old PG release on a current operating system? Do yourself a favor and move up to some recent release.