Jaume Catarineu wrote:
> The following bug has been logged online:
>
> Bug reference: 2927
> Logged by: Jaume Catarineu
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.1
> Operating system: Linux srvca01 2.6.11.4-20a-smp #1 SMP Wed Mar 23
> 21:52:37 UTC 2005 i686
James Becerra wrote:
> The following bug has been logged online:
>
> Bug reference: 2929
> Logged by: James Becerra
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Windows 2003 Server
> Description:Error opening 5432 port
> Details:
>
The following bug has been logged online:
Bug reference: 2927
Logged by: Jaume Catarineu
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Linux srvca01 2.6.11.4-20a-smp #1 SMP Wed Mar 23
21:52:37 UTC 2005 i686 i686 i386 GNU/Linux
Description:
Hello,
I'm wondering if anyone has experienced the same problem and is it fixed
in the new Postgres release (We use Posgtgres 8.1.2, psqlodbc.so 7.2.5
(moving to 8.2.200), unixODBC 2.2.11 (moving to 2.2.12), running on
Linux OS.):
We have a recurring problem that the return type (a customer def
The following bug has been logged online:
Bug reference: 2930
Logged by: Maciej Babinski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: CentOS 4.4 (linux 2.6.9)
Description:Hash join abyssmal with many null fields.
Details:
Hash join of c
The following bug has been logged online:
Bug reference: 2929
Logged by: James Becerra
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows 2003 Server
Description:Error opening 5432 port
Details:
Hi,
Let me explaint my problem.
I usu
The following bug has been logged online:
Bug reference: 2926
Logged by: Mandeep
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: MS Windows XP
Description:E_OUTOFMEMORY
Details:
Hi,
I am creating a sample application to connect a simple RO
Hello,
I'm wondering if anyone has experienced the same problem and is it fixed
in the new Postgres release (We use Posgtgres 8.1.2, psqlodbc.so 7.2.5
(moving to 8.2.200), unixODBC 2.2.11 (moving to 2.2.12), running on
Linux OS:
We have a recurring problem that the return type (a customer defin
Jeff Trout <[EMAIL PROTECTED]> writes:
> On Jan 24, 2007, at 12:24 PM, Tom Lane wrote:
>> Hmm. This should yield an error (SQL function not returning the type
>> it claims to), and we probably should plug the hole by invoking
>> check_sql_fn_retval every time not just at creation.
> The really cu
On Jan 24, 2007, at 12:24 PM, Tom Lane wrote:
Jeff Trout <[EMAIL PROTECTED]> writes:
I just ran across this, and I do not think it is entirely a PG bug or
even something that the backend can detect and handle.
The problem stems from swapping a table definition from under a
function.
Hmm. Th
Jeff Trout <[EMAIL PROTECTED]> writes:
> I just ran across this, and I do not think it is entirely a PG bug or
> even something that the backend can detect and handle.
> The problem stems from swapping a table definition from under a
> function.
Hmm. This should yield an error (SQL function n
I wrote:
> Nonetheless, the code is certainly giving wrong answers for 4-byte
> characters. Will go fix...
I've applied the attached patch for 8.1, and related patches in all
supported branches.
regards, tom lane
Index: wchar.c
==
I just ran across this, and I do not think it is entirely a PG bug or
even something that the backend can detect and handle.
The problem stems from swapping a table definition from under a
function. I had a rather large table that had a number of double
precision (dp) fields, and in a battl
13 matches
Mail list logo
