On Wed, 23 Apr 2008, valgog wrote:
Is it possible to implement the setStatementTimeout() as somethig
like:
s = c.prepareStatement("SELECT set_config('statement_timeout',
, false);" );
s.executeQuery();
c.commit();
Not really. This sets a global timeout for all queries while the JDBC API
how to dump it ???
pg_dump is not working :
pg_dump: query to obtain list of schemas failed: ERROR: more than one
row returned by a subquery used as an expression
Tom Lane пишет:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
[EMAIL PROTECTED] wrote:
I don't know how, but i got 2 postgr
The following bug has been logged online:
Bug reference: 4127
Logged by: Jacob Champlin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.11
Operating system: SuSE 10.1
Description:pg_dumpall -c unable to be restored without error
Details:
In 8.0 I would do
"Jacob Champlin" <[EMAIL PROTECTED]> writes:
> psql -f restore.sql
> results in:
> psql:/var/lib/pgsql/backups/restore.sql:11: ERROR: current user cannot be
> dropped
> psql:/var/lib/pgsql/backups/restore.sql:12: ERROR: role "postgres" already
> exists
> psql:/var/lib/pgsql/backups/restore.sql:
And if this is expected correct behavior it shouldn't throw an error
This is especially problematic for automated processes, in which you
only want to know when they fail.
Its possible to ignore error messages, but then when something real does
go wrong you lose those.
Don't get me wron
The following bug has been logged online:
Bug reference: 4128
Logged by: Gary Jay Peters
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Linux/Debian
Description:The postmaster.opts.default file is begin ignored
Details:
1st, I already h
"Gary Jay Peters" <[EMAIL PROTECTED]> writes:
> As I understand it, the only the "pg_ctl" command uses the
> "postmaster.opts.default" file; it uses the arguments
> within "postmaster.opts.default" when spawning the "postmaster" process.
Actually, I'd vote for ripping out that "feature" altogether
Tom Lane wrote:
> "Gary Jay Peters" <[EMAIL PROTECTED]> writes:
> > As I understand it, the only the "pg_ctl" command uses the
> > "postmaster.opts.default" file; it uses the arguments
> > within "postmaster.opts.default" when spawning the "postmaster" process.
>
> Actually, I'd vote for ripping o
Tom Lane wrote:
> We've mostly deprecated setting options on the postmaster command
> line already, so why do we need another obscure way to do that?
As long as we support the pg_ctl -o option, the file still necessary so that
you get the same options after a restart.
--
Sent via pgsql-bugs mai
> From: "Peter Koczan" <[EMAIL PROTECTED]>
> To: pgsql-bugs@postgresql.org
> Date: Wed, 23 Apr 2008 17:17:01 GMT
> Subject: BUG #4126: KRB5/GSSAPI authenication fails for multipart kerberos
> principals
>
> When trying to connect to an 8.3 server using a multipart Kerberos principal
> (e.g. ator
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> We've mostly deprecated setting options on the postmaster command
>> line already, so why do we need another obscure way to do that?
> As long as we support the pg_ctl -o option, the file still necessary so that
> you get the same
11 matches
Mail list logo
