Milen A. Radev wrote:
> raf :
> > hi,
> >
> > in my database, normal users can't select, insert, update or
> > delete anything directly. they can only call functions which
> > are all security defining functions which give access to the
> > data. that's the way i like it.
> >
> > how
>>> raf wrote:
> revoke all privileges on schema public from public;
> revoke all privileges on schema public from staff; -- staff is a
role
>
> then i get two warnings:
>
> WARNING: no privileges could be revoked for "public"
> WARNING: no privileges could be revoked for "public"
>
Marc Mamin wrote:
> There are 2 features that would be helpfull in my case:
>
> - define vacuum properties on table groups rather than on given tables:
>
> For example, I don't want to vacuum daily tables which can be
> identified with a regexp:
> tablename ~ '\.*d_[0-9]{8}'
Hmm. I
Hello,
I'm getting this message when I try to back up one of my databases.
Is there something I can do about this?
bash-3.00# pg_dump -U postgres citesrch > /pgdump/citesrch_bk.sql
pg_dump: failed sanity check, parent table OID 131956046 of pg_rewrite
entry OID 131956048 not found
Thanks
Can you perform queries against tables in that database? You may have
to poke around in the systems tables for the object ids in question.
-lee
On Wed, Feb 4, 2009 at 2:32 PM, Carol Walter wrote:
> Hello,
>
> I'm getting this message when I try to back up one of my databases. Is
> there somethi
Kevin Grittner wrote:
> >>> raf wrote:
> > revoke all privileges on schema public from public;
> > revoke all privileges on schema public from staff; -- staff is a role
> >
> > then i get two warnings:
> >
> > WARNING: no privileges could be revoked for "public"
> > WARNING: no privi
