Steve Peterson wrote:
> Any known way to log at the JDBC level? When I get a little time I'm
> going to write a test that bypasses Eclipse and SQLExplorer.
Pass 'logLevel=2' as a URL parameter in the JDBC URL; that will log all
protocol-level messages sent and received, including the query text.
I'll recompile with the trace that's no problem,
and install the patched release tonight.
After your last email, I've excluded the postgreSQL
directory from the antivirus because I could do it without
rebooting.
I was also sometimes getting read/write or open
error Invalid argument without the s
""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Yes, there is an antivirus software on the machine, a reboot is needed
> when it's turned off,
> I'll be allowed to reboot it tonight or I'll do it sooner if it crashes
> before that.
>
> There are around
Jose Vasquez wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1939
> Logged by: Jose Vasquez
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: linux
> Description:enhancement
> Details:
>
> bizgres database table
The following bug has been logged online:
Bug reference: 1939
Logged by: Jose Vasquez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: linux
Description:enhancement
Details:
bizgres database table partition is very full.
postgresql 8.1 ned
Yes, there is an antivirus software on the machine, a reboot is needed when
it's turned off,
I'll be allowed to reboot it tonight or I'll do it sooner if it crashes
before that.
There are around 15 connections to PostgreSQL when it crashes but most are
idle
there may be a few inserts but no
Steve Peterson wrote:
> Any known way to log at the JDBC level? When I get a little time I'm
> going to write a test that bypasses Eclipse and SQLExplorer.
>
> On Wed, 5 Oct 2005, Oliver Jowett wrote:
>
> > Alvaro Herrera wrote:
> > > On Fri, Sep 30, 2005 at 10:37:05PM -0500, Steve Peterson wrot
On Tue, Oct 04, 2005 at 08:29:23PM +0100, Jeff MacDonald wrote:
> I did a backup from 7.3.2 using pg_dumpall.
>
> When I did a restore all of my timestamps that were defaulted to now(); were
> now defaulted to the time that I piped my dump back into postgres.
>
> Meaning the now() was parsed inst
