On Mon, 17 Jan 2005 23:44:37 -0500, Madison Kelly <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
> > Michael Fuhr <[EMAIL PROTECTED]> writes:
> >
> >>On Mon, Jan 17, 2005 at 09:03:17PM -0500, Madison Kelly wrote:
> >>
> >>>Is there any way I can log and/or display database calls for a
> >>>specific d
Tom Lane wrote:
Madison Kelly <[EMAIL PROTECTED]> writes:
Where /is/ the log file?
It depends. If you selected syslog logging then it's wherever syslog is
configured to put the messages. Otherwise, it's wherever the
postmaster's stderr output is being sent.
A fairly annoying property of the curr
On Jan 18, 2005, at 13:57, Michael Fuhr wrote:
On Mon, Jan 17, 2005 at 11:41:34PM -0500, Tom Lane wrote:
You forgot that ALTER DATABASE has this same option. It might be that
ALTER USER is just as convenient, or even more so, for Madison's
problem
... but it *can* be set at the database scope if
On Mon, Jan 17, 2005 at 11:41:34PM -0500, Tom Lane wrote:
>
> You forgot that ALTER DATABASE has this same option. It might be that
> ALTER USER is just as convenient, or even more so, for Madison's problem
> ... but it *can* be set at the database scope if needed.
Drat, thanks for the reminder.
Madison Kelly <[EMAIL PROTECTED]> writes:
> Where /is/ the log file?
It depends. If you selected syslog logging then it's wherever syslog is
configured to put the messages. Otherwise, it's wherever the
postmaster's stderr output is being sent.
A fairly annoying property of the current RPM packa
Tom Lane wrote:
Michael Fuhr <[EMAIL PROTECTED]> writes:
On Mon, Jan 17, 2005 at 09:03:17PM -0500, Madison Kelly wrote:
Is there any way I can log and/or display database calls for a
specific database?
I don't know of a way to enable logging for a specific database,
but you can enable logging for
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Mon, Jan 17, 2005 at 09:03:17PM -0500, Madison Kelly wrote:
>> Is there any way I can log and/or display database calls for a
>> specific database?
> I don't know of a way to enable logging for a specific database,
> but you can enable logging for a s
On Mon, Jan 17, 2005 at 09:13:19PM -0600, Tony Caduto wrote:
> This is great info, is there a way to get the log back via a SQL call?
> It would be pretty cool if there was a way to have the log go to a table
> instead of a file.
Not that I'm aware of, but you could write a function to read the
On Mon, Jan 17, 2005 at 10:06:20PM -0500, Paul Tillotson wrote:
> I use ethereal (on the client--although it would possibly work on the
> server too) in such a case. It's a bit messy but if you just want to
> see what SQL statements were being run, then it works.
Caveats: sniffers like etherea
Michael,
This is great info, is there a way to get the log back via a SQL call?
It would be pretty cool if there was a way to have the log go to a table
instead of a file.
Tony Caduto
Michael Fuhr wrote:
ALTER USER johndoe SET log_statement TO TRUE; -- 7.x
ALTER USER johndoe SET log_statement TO
Madison Kelly wrote:
Hi all,
This is probably an easy question but I couldn't my answer in the
docs (I probably looked right at it...).
Is there any way I can log and/or display database calls for a
specific database? I am trying to debug a third party program and I
can see that the problem
On Mon, Jan 17, 2005 at 09:03:17PM -0500, Madison Kelly wrote:
> Is there any way I can log and/or display database calls for a
> specific database?
I don't know of a way to enable logging for a specific database,
but you can enable logging for a specific user or session. For
example, you cou
Hi all,
This is probably an easy question but I couldn't my answer in the
docs (I probably looked right at it...).
Is there any way I can log and/or display database calls for a
specific database? I am trying to debug a third party program and I can
see that the problem probably has somethi
13 matches
Mail list logo
