Hello,
I've also come across the bigint/index bug where an index on
table(bigint_col) is ignored for
explain select * from table where bigint_col = 83
results in a "Seq Scan" while
explain select * from table where bigint_col = '83'
and explain select * from table where bigint_col = 83::bigint
I built 7.3B2 from CVS and ran initdb: it fails. Here's an example of
the console session:
demo >>>
$ initdb -D /usr/local/pgdata
The files belonging to this database system will be owned by user "nferrier".
This user must also own the server process.
The database cluster will be initialized wi
After days of researching this problem all I find is that knowbody has done
this successfully and documented it for me to find. I cannot determine if it
is a bug or my incorrect development structure to blame.
I would like to pass character data from postgreSQL 7.1.3 user function into a
C pro
THis is with reference to the earlier email about error during compiling
postgresql, I used the following configuration parameters.
Additional information
Thanks again,
-V
#!/bin/bash
./configure --enable-recode --enable-multibyte --with-CXX --with-perl --enable-odbc
--with-java --with
i have installed cygwin with posgresql 7.2.1-2 on windows 2000 ..with the user name muhammad .
after that i have installed pgODBC AND Pgadmin2 ..
i have initilaized new data base(testdb1) and then run postmaster it gives me very stange error ..please find the attachment ..
yesterday it was working
I had two separate problems while compiling postgresql on my machine,
information attached. Once, java refused to recognize the symbol
javax.transaction.RolledbackException, and the second time some kind of VM
error occurred. I am running a RedHat Linux 7.3 (2.4.8-10), with
j2sdk1.4.1.
Please l
Hello,
I have tried for days to get postgresql working on OpenBSD on an old sparc32
box which I use to learn OpenBSD and Postgresql. I'll try to describe the
steps I went through as precise as possible.
First, I bought a sparc station 2 - an old box in a good condition, I've run
debian gnu/l
Nic Ferrier <[EMAIL PROTECTED]> writes:
> DEBUG: inserting column 7 value '0'
> DEBUG: Typ != NULL
> ERROR: Bad float4 input format -- underflow
Hm. This is evidently failing this test:
static void
CheckFloat4Val(double val)
{
if (fabs(val) > FLOAT4_MAX)
elog(ERROR, "
"Bill Schneider" <[EMAIL PROTECTED]> writes:
> This seems to be a well-known and documented issue. Are there already plans
> to fix this in an upcoming release?
Yes.
> Is the problem here in the optimizer itself, or in the parser?
The problem is that the query is interpreted as "int8col int84e
"Josh Berkus" <[EMAIL PROTECTED]> writes:
> Postgres terminated my back-end connection to the server when it
> reached the VACUUM statement.
> Next, I reconnected. I was quite surprised to discover that Postgres
> had *not* rolled back the changes made by the function before it
> crashed.
Yeah.
Folks,
I just encountered a very interesting bug in ver 7.2.1.
As an experiment, I tried running a VACCUUM ANALYZE on a table inside a
Function after the function had made a large number of updates to that
table. I assumed that this wouldn't work, but I thought I'd give it a
try.
It did not w
Josh Berkus wrote:
> Folks,
>
> I just encountered a very interesting bug in ver 7.2.1.
>
> As an experiment, I tried running a VACCUUM ANALYZE on a table inside a
> Function after the function had made a large number of updates to that
> table. I assumed that this wouldn't work, but I thought
We will have point-in-time recovery in 7.4. We are just releaseing
7.3beta now.
---
Jon Watte wrote:
>
> Again, thank you for your reply. I am copying the bugs list in the
> hope that some ray of insight will hit.
>
> I
13 matches
Mail list logo
