Bhushan Verma wrote:
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> connection to server was lost
Look in the PostgreSQL server logs for more information. It's probably
in /var/log/postgresql or someth
Bhushan Verma wrote:
> I am doing some database related queries and this is working fine at fedora
> core 4.
> But the same database queries giving the FATAL error on fedora 9.
>
> If I restarts the database on fedora core 9 then this is perfectlry working
> without giving any error.
>
> My postg
Hi All,
I am doing some database related queries and this is working fine at fedora
core 4.
But the same database queries giving the FATAL error on fedora 9.
If I restarts the database on fedora core 9 then this is perfectlry working
without giving any error.
My postgres version is
On Fedora co
The following bug has been logged online:
Bug reference: 4876
Logged by: Jim Michaels
Email address: jmich...@yahoo.com
PostgreSQL version: 8.3.7-1
Operating system: windows XP Pro SP3
Description:author of MD5 says it's seriously broken - hash
collision resistance pr
"Brad Bowman" writes:
> There seems to be an oversight in the dml-update
> document.
> http://www.postgresql.org/docs/8.3/interactive/dml-update.html
> doesn't link to
> http://www.postgresql.org/docs/8.3/interactive/sql-update.html
> while both dml-insert and dml-delete do link to their
> respe
This is how Oracle does it. The equivalent data type to BYTEA in Oracle
is RAW. You can use a host variable to specify the length as well.
EXEC SQL BEGIN DECLARE SECTION;
unsigned char *bytea_hostvar;
EXEC SQL VAR bytea_hostvar IS RAW(1024);
EXEC SQL END DECLARE SECTION;
ANSI SQL 92 specif
Tom Lane wrote:
> Magnus Hagander writes:
>> Attached is an updated patch that does both of these.
>
> This looks reasonably sane to me, and I'm satisfied with the testing
> that's been done. No objection from here.
Applied.
//Magnus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresq
Hi i downloaded the program but i cant install cause i need a password. so i
create onw buy nothing, wrong password wrong password,
8 months ago y install it the but now i cant remenber the password, i
installed in otrer computer? why cant i installed here?
Please help me
The following bug has been logged online:
Bug reference: 4873
Logged by: Brad Bowman
Email address: postg...@bereft.net
PostgreSQL version: 8.3
Operating system: n/a
Description:docs: no link from dml-update to sql-update
Details:
There seems to be an oversight in t
"Roman Galeev" writes:
> I've constantly got messages like this:
> 2009-06-23 20:43:42 YEKST WARNING: database "testing" must be vacuumed
> within 10532638 transactions
> 2009-06-23 20:43:42 YEKST ÐÐÐСÐÐÐÐÐ: To avoid a database shutdown,
> execute a full-database VACUUM in "testing".
"Nick Roosevelt" writes:
> I am getting bad results for distance between point and lseg. As you can
> see below, the first result is correct, and the second is clearly not.
Hmm ... what it looks like to me is that there's an ancient thinko
in dist_ps_internal(). It's trying to calculate the slo
How about something like this? I switched to using LocalAlloc() in all
places to be consistent, instead of mixing heap and local. (Though per
doc, LocalAlloc is actually a wrapper for HeapAlloc in win32).
Our patches crossed. Although, in my patch I left the allocation scheme
alone since I
DWORD len = GetLengthSid(pTokenUser->User.Sid)
*ppSidUser = (PSID) HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, len);
CopySid(len, *ppSidUser, pTokenUser->User.Sid);
I attached a patch for this. Although, I did not use CopySid. Instead,
I changed GetUserSid to GetTokenUser. AddUserToDacl(
Andrew Chernow wrote:
> TAKATSUKA Haruka wrote:
>> Hi.
>>
>> We found the unbalance of xxAlloc and xxFree at AddUserToDacl() in
>> src/port/exec.c (of current HEAD code).
>>
>> psidUser is a pointer of the element of a TOKEN_USER structure
>> allocated by HeapAlloc(). The FreeSid() frees a SID al
The following bug has been logged online:
Bug reference: 4874
Logged by: Roman Galeev
Email address: i...@ncom-ufa.ru
PostgreSQL version: 8.1
Operating system: Debian Sarge
Description:vacuum doest work
Details:
I've constantly got messages like this:
2009-06-23 20
Magnus Hagander writes:
> Attached is an updated patch that does both of these.
This looks reasonably sane to me, and I'm satisfied with the testing
that's been done. No objection from here.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.o
Am Dienstag, 23. Juni 2009 14:17:15 schrieben Sie:
> Attached is an updated patch that does both of these.
It works for me, but I could test it only with OpenSSL 0.9.8g.
Moreover I tested the SSL-renegotiation, and it works quite fine with an
engine too - as long as I don't pull the smartcard wi
At present, a specific error, crash or trouble seems not to have
happened.
The reason its not crashing is that most, if not all, windows allocation
functions know which addresses belong to them. FreeSid is actually
documented as returning NULL on success. On failure it returns the
address
Tom Lane wrote:
> Magnus Hagander writes:
>> On 22 jun 2009, at 18.05, Tom Lane wrote:
>>> I'm also a bit concerned about wrapping a struct
>>> field inside such an #if, as that's likely to cause hard-to-debug
>>> problems if two compilations read libpq-int.h with different #define
>>> environmen
Tom Lane wrote:
> Magnus Hagander writes:
>> Lars Kanis wrote:
>>> Maybe version 2 (my initial patch) could be an alternative ?
>
>> Well, based on the "we don't know which different versions of openssl
>> it'll break with", version 2 is no better than version 3 :(
>
> Yeah, if we do anything I
Rick Levine wrote:
> ECPG does not handle BYTEA columns properly. When I encode a unsigned char
> array using PQescapeByteaConn and send it to the server, it is not stored as
> the original bytes, but rather is stored as the escaped string (much
> larger).
Yeah, that's clearly not the right way t
Hello,
Please can you assist on following questions.
* do you any tool to check postgreSQL database integrity check?
* how do we confirm that dump file is proper data?
* do you any doc to check the integrity of psql db?
Venkat Prasad
CREDIT SUISSE
SCM Systems Support
The signature level 4
Cha
The following bug has been logged online:
Bug reference: 4872
Logged by: Nick Roosevelt
Email address: nro...@thepinc.com
PostgreSQL version: 8.2.5
Operating system: Linux
Description:Geometric function problem
Details:
I am getting bad results for distance between
23 matches
Mail list logo
