[ADMIN] FW: vacuum problems

i have re-named the ssmsact table to ssmsactold, dropped table ssmsact and associated index, tried vacuuming again and still get the same error. i then re-created ssmsact table and indexes w/ the SAME NAMES as used originally, populated it with values from ssmsactold, and checked that all val

[ADMIN] FW: vacuum problems

-Original Message- From: JT Kirkpatrick [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, December 28, 1999 10:00 AM To: '[EMAIL PROTECTED]' Subject:vacuum problems any idea how to correct this problem? system seems to be working fine, but nightly vacuums give us this error mess

Re: [ADMIN] mixed case table name problem

On Tue, 28 Dec 1999, Ruben Fagundo wrote: > > I was wondering if anyone has seen this problem. I created a Postgres > Database, and when I run > > vacuum -z -v db_name --table mixedTablename > > I am told: > > NOTICE: vacuum: Table not found vacuum --table \"TableName\" ...etc

[ADMIN] mixed case table name problem

I was wondering if anyone has seen this problem. I created a Postgres Database, and when I run vacuum -z -v db_name --table mixedTablename I am told: NOTICE: vacuum: Table not found However I can see the table with pgaccess, and I can edit it with pgaccess, but vacuum reports that all the ta

[ADMIN] user access to db restriction

Hi! Please explain me how to restrict user access to database? I mean to permit user to connect some db and prohibit to connect another. By default each user can connect any db and read scheme as minimum... Its not good in multiuser envirinment... SKiller -- Sergei Keler