| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andre Schubert <andre(at)km3(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Problems with PGOPTIONS |
| Date: | 2003-01-15 16:19:29 |
| Message-ID: | 5306.1042647569@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Andre Schubert <andre(at)km3(dot)de> writes:
> Ok, but is there another way to enable STATS_ROW_LEVEL for a special
> backend not connecting as superuser ?
No: the code is deliberately designed to prevent that, on the grounds
that it'd be a security flaw (non-superusers should not be allowed to
hide their activities from the DBA).
There's nothing to stop you from making a private version with
stats_row_level downgraded to an ordinary unprotected SET variable,
though, if that seems more appropriate to your needs. See its entry in
src/backend/utils/misc/guc.c and change it from SUSET to USERSET
category (from memory; check spelling in src/include/utils/guc.h).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah. | 2003-01-16 06:57:34 | Re: How Copy 7.3 Schemas? |
| Previous Message | Gareth Kirwan | 2003-01-15 15:52:43 | pg_dumpall and large flat file |