On Wed, Oct 12, 2005 at 11:18:02 +0200,
Pieter-Jan Savat <[EMAIL PROTECTED]> wrote:
>
>
> Tom Lane wrote:
>
> >Pieter-Jan Savat <[EMAIL PROTECTED]> writes:
> >
> >
> >>2005-10-11 17:22:28 CEST ([EMAIL PROTECTED]) [2005-10-11 17:08:49 CEST]
> >>PANIC: right sibling's left-link doesn't match
> Possibly the folks on pgsql-jdbc could help you with
> that.
>
> regards, tom lane
sincere thanks to you tom lane
I checked all the shell programs in the system which
running standalone from SUN application server. Finally
find the answer. One of those shell programs uses
On Tue, Oct 25, 2005 at 22:36:58 -0500,
"Jim C. Nasby" <[EMAIL PROTECTED]> wrote:
> We need the output of EXPLAIN ANALYZE, from both versions if possible.
Isn't that going to be a problem in this case since it seems unlikely
that EXPLAIN ANALYZE will finish in a reasonable amount of time?
>
>
On 26.10.2005 16:06, Tharo Mohono wrote:
I just wanted to know how possible it is to install
postgres on the windows server and have some terminals
conneting to the server to query the database,
Starting with 8.0, there is a native Windows version of PostgreSQL.
and if possible, could you ple
acemeicn <[EMAIL PROTECTED]> writes:
> I tried excuting the long sql on the console and a DB tool
> called CSE(Common SQL Environment), it worked.
> but in a java program using JDBC connection it doesn't
> work.
Possibly the folks on pgsql-jdbc could help you with that.
r
Hi,
I just wanted to know how possible it is to install
postgres on the windows server and have some terminals
conneting to the server to query the database, and if
possible, could you please give me the steps on how to
do that.
Thank you.
__
i want to unsubscribe to this mailing list
thanks
Sois Heureux, Souris, Aime. ne
réfléchis pas trop,Pries et laisse DIEU diriger ta vie. ça marche à tousles
coups. sisqo
_
MSN Messenger : discutez en direct avec vos amis !
h
> The best guess I have is that this is a failure in
> Solaris' syslog.
> There is certainly no such message anywhere in the
> Postgres backend
> code. Try changing your syslog setting to 0 (log
> only to stderr)
> and see if logging to a plain file works better.
>
> BTW, PG 7.3.4 is pretty darn
