On Sat, Jun 19, 2010 at 5:28 AM, Phoenix Kiula wrote:
>> It's far easier to adjust the logging.
>>
>> psql mydb
>> alter mydb set log_statement='mod';
>
>
>
> Thanks Scott.
>
> Two questions:
>
> 1. Will this log_statement='mod' be a permanent thing, or when I have
> done my testing and identifyin
> It's far easier to adjust the logging.
>
> psql mydb
> alter mydb set log_statement='mod';
Thanks Scott.
Two questions:
1. Will this log_statement='mod' be a permanent thing, or when I have
done my testing and identifying the problem SQL, I can set it back to
default so not too much logging
Scott Marlowe writes:
> On Mon, Jun 14, 2010 at 5:55 PM, Phoenix Kiula
> wrote:
>> My question: how can I set up a "RULE" so that when a specific column
>> is updated, a separate table also logs which update SQL was issued?
> It's far easier to adjust the logging.
Or, if you're worried about a
On 06/14/2010 06:55 PM, Phoenix Kiula wrote:
Hi
I'm having some issues with a code base where several different
programs are updating one "status" column in the DB with their code.
Mostly this is working, but in some cases the status column in a DB is
getting updated when it shouldn't have been,
On Mon, Jun 14, 2010 at 5:55 PM, Phoenix Kiula wrote:
> Hi
>
> I'm having some issues with a code base where several different
> programs are updating one "status" column in the DB with their code.
> Mostly this is working, but in some cases the status column in a DB is
> getting updated when it s
Hi
I'm having some issues with a code base where several different
programs are updating one "status" column in the DB with their code.
Mostly this is working, but in some cases the status column in a DB is
getting updated when it shouldn't have been, and we're trying to
locate which program did i