This has to be the most insightful and well thought out bug report I've
ever read.
Maykon wrote:
The following bug has been logged online:
Bug reference: 2604
Logged by: Maykon
Email address: [EMAIL PROTECTED]
PostgreSQL version: --
Operating system: win & linux
Descriptio
Isn't that expected? Your query will try to update row 3 first and set
the primary key to 5, which in fact would violate the primary key
constraint on that table.
Laurence Dawson wrote:
And then try an update:
lstore=> select * from test.test;
a
1
2
3
4
5
6
7
8
9
10
(1
Someone discovered our diabolical plot to secretly install postgres on
every computer across the globe! Quickly! Dispatch the Deadly Viper
Assassination Squad to silence him!
Vaccaro wrote:
I never download your product i don't even know what it is. When i
started my computer up i saw 2 new a
Place the postgresql.* files into the ~/.postgresql directory on the
client side.
So that answers a).
b) The client shouldn't be looking for root.crt
c) That should do it. If you have any more questions feel free to email
me off the list and I'll see what else ya need help with.
Anyone else notice breakage from 8.0.0 to 8.0.1 using msvc(6)? Was just
about to update my client libraries and I got an unresolved external
symbol SHGetFolderPath in fe-connect.c, wasn't 8.0.0 using
SHGetSpecialFolderPath?
---(end of broadcast)--
Yeah I already tried removing the ifdef's...oh BOY was it not happy :'(
Tom Lane wrote:
"T.J." <[EMAIL PROTECTED]> writes:
Which leads me to my next question; that function client_cert_cb, does
it ever get executed on windows? :)
Um. Looks like someone ifdef&
ng of that function there is a:
#ifdef WIN32
return 0;
#else
... (function)
return 1;
#endif
Tom Lane wrote:
"T.J." <[EMAIL PROTECTED]> writes:
Not to my knowledge. By the way, for future reference on windows it
looks for the cert/key in the linux equivalent of
`pwd`/
h the same resulting error.
Bruce Momjian wrote:
Did we ever find the solution to this, or did anyone find the cause?
-------
T.J. wrote:
Having some problems (still, hehe) getting SSL to work properly on
windows in the new 8.0
this file should automatically be
rebuilt. Check if it's corrupted, and try removing it and rebuild that
directory (first, then the ecpg dir that is failing).
//Magnus
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of T.J.
Sent: den 2 januari 2005
The following bug has been logged online:
Bug reference: 1369
Logged by: T.J.
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:RC3 Compilation fails on mingw
Details:
Tested RC2 and RC3 --with-openssl configured. RC2
Having some problems (still, hehe) getting SSL to work properly on
windows in the new 8.0 (all vers) environment (where cert/key is required).
On the client side when not finding the certificate/key psql would
report the SSL error sslv3 alert handshale failure. After I figured out
where psql wa
To clarify, what I have experienced was in all versions of 8.0.0.beta,
it did not just happen between 3 to 4. It was the change from 7.4 to
8.0. The error was not just windows based as I built psql on a seperate
linux machine communicating with a linux server and got the same
results. I created
12 matches
Mail list logo
