Re: limit the database size

Correct me if I am wrong but limiting storage size under the DB is not
always the right thing to do. Once my db ran out of space when
vaacum-ing at night, and one of the indexes damaged, so, I could not do
selects using that index, i had to drop it, add some storage, recreate,
vacumanalyze, etc.

Laszlo Hornyak

Rudi Starcevic wrote:

> Hi,
>
> If you compile/re-compile all databases are accesssible from one port.
> The system table pg_database stores the path to the 'base' dir which
> can be in the user's dir.
>
> Also in the pg_database table you can update the datdba field to
> change the owner of the database.
> An example where this is very cool is if the user logs into their
> database via a web interface like
> phpPgAdmin they can log into just their database and not anyone else's.
> Pretty much ideal for a hosting situation.
>
> Does anyone have the C compile flags handy ?
>
> Cheers
> Best regards
> Rudi.
>
>
>
>
> Oliver Elphick wrote:
>
>> On Fri, 2003-10-10 at 07:13, Laszlo Hornyak wrote:
>>
>>
>>> Hi!
>>>
>>> I believe you don`t need to recompile, just
>>> export PGDATA=/home/me/pgdata
>>> pg_initdb
>>> pg_ctl start
>>> and ready to go.
>>>
>>
>>
>> If you do this, each separate instance needs a different port. That can
>> be set in $PGDATA/postgresql.conf.
>>
>> When you connect to the server (with psql or another frontend) you
>> specify the correct port for the server you want.
>>
>> psql -p 5433 -d mydatabase
>>
>> or
>>
>> export PGPORT=5433
>> psql -d mydatabase
>>
>>
>>
>>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly