Hello There,
I noticed that if I have rules set on a table and if I do a cluster
index-name on the table, it deletes all the rules. Is this normal? I am
just wondering as I would like to cluster the data occasionally. I am not
sure if this is a bug, or it is supposed to drop all the
Following is an updated list of the messages to be channeled by the proposed logging
system.
THESE AND *ONLY* THESE are slated for implementation. If you have items you want
included, PLEASE LET ME KNOW! As it stands, this is a pretty minimal set.
Bear in mind that the logger is NOT a debugger.
Tom Lane wrote:
>
> Tim Holloway <[EMAIL PROTECTED]> writes:
> >> Note that logging into a table is harder than you might think.
>
> > I guess I should have mentioned - at least in its initial incarnation,
> > cowardice forbids me to attempt reading or writing PostgreSQL tables
> > directly. The
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Why not do something similar to what we are doing with pg_shadow? If I
> remember the logic right, when you update pg_shadow, one ofits "steps" is
> to dump it to a text file so that postmaster can read it?
I thought about suggesting that, but IIRC
Why not do something similar to what we are doing with pg_shadow? If I
remember the logic right, when you update pg_shadow, one ofits "steps" is
to dump it to a text file so that postmaster can read it? this should
make it easy for one user/database to have one logging set, while another
doesn'
Tim Holloway <[EMAIL PROTECTED]> writes:
>> Note that logging into a table is harder than you might think.
> I guess I should have mentioned - at least in its initial incarnation,
> cowardice forbids me to attempt reading or writing PostgreSQL tables
> directly. The logfile design is designed to
