The following bug has been logged online:
Bug reference: 1406
Logged by: manikanti sreedhar reddy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Windows
Description:subsequent WHEN/ELSE is getting validated, eventhough
prior WHEN conditio
PGSQL version is 8.0.0 beta4.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
"manikanti sreedhar reddy" <[EMAIL PROTECTED]> writes:
> Let us take an example:
> select (CASE WHEN POSITION('/' IN '172.16.1.1-172.16.1.25')=0 THEN FALSE
> ELSE (INET('172.16.1.1-172.16.1.25'::INET) >> INET('internalnetwork'::INET)
> ) END);
I get:
regression=# select (CASE WHEN POSITION('/'
The following bug has been logged online:
Bug reference: 1405
Logged by: daniel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: windows xp professional
Description:instalation
Details:
error on installation
do not install
--
The following bug has been logged online:
Bug reference: 1401
Logged by: Sirilug
Email address: [EMAIL PROTECTED]
PostgreSQL version: from linux 9.0
Operating system: linux 9.0
Description:Thai language
Details:
1. can not sort thai language on ก-ฮ
2. when input tha
The following bug has been logged online:
Bug reference: 1403
Logged by: Phil
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8
Operating system: windows
Description:Failed to create process: 2
Details:
Running the msi installer gave thie above message
---
The following bug has been logged online:
Bug reference: 1402
Logged by: raxfar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0-rc2
Operating system: windows 2000
Description:getPrecision don't work
Details:
have
java.sql.ResultSetMetaData _oMetaData.getP
Michael,
On 16/1/05 12:48 AM, "Michael Fuhr" <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 14, 2005 at 11:31:05PM -0500, Tom Lane wrote:
>> "Fahad G." <[EMAIL PROTECTED]> writes:
>>> -- Indexes
>>> CREATE INDEX jobstat_lc_q4_2004_jobid ON jobstat_lc_q4_2004 USING btree
>>> (jobid);
>>> CREATE INDEX j
Tom,
You're right. Here's what explain says:
hpc=> explain SELECT fetchtime, curr_walltime FROM jobstat_lc_q4_2004 WHERE
jobid = 213213 ORDER BY fetchtime DESC;
QUERY PLAN
-
The following bug has been logged online:
Bug reference: 1404
Logged by: T.Russell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: FreeBSD 5.3
Description:pg_dump: dump order/dependence for a UDF
Details:
for example, there is the table:
Hi,
Forgive me my poor English for writing.
Sees, below, that it seems to have one bug in set transform_null_equals
or, then, in <> NULL.
This fact occurs in Versions: 7.4.5 and 8.0.0-rc2.
-- Creation with transform_null_equals set to off
set transform_null_equals to OFF;
--drop table cnt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm running PostgreSQL 7.4.6 on RHEL 4 Beta 2. There seems to be a
bug, or call it inconsistentcy with the documentation, in the
interval data type. According to
http://www.postgresql.org/docs/7.4/static/datatype-datetime.html, the
resolution of
Simon Riggs wrote:
Are you running any plug-ins or have you altered the server code in any
way? This might be additional Languages added, Functions written in
those languages or SPI code. Those must draw the most suspicion for an
error of this type.
"select * from pg_language" shows only internal,
I downloaded the new postgress, Installed it and did as you commanded at the
cmd prompt;
postmaster -U postgres -i
and got this message:
(Execution of Postgres SQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivleged user ID to prevent possi
Hello,
I'm having an unexpected behaviour when executing an 'after delete' trigger.
In PostgreSQL 8.0.0beta5 documentation, section 33.2 "Visibility of Data
Changes", it is said that "When a row-level after trigger is fired, all
data changes made by the outer command are already complete, and are
I built 8.0.0rc5 on FreeBSD 4.8. It built with no errors. I then
tried psql using another host running postgresql 7.1.3 and I get the
goofy error message shown below. Other backslash commands seem to work
(ie. \? \e \q).
$ psql -h host-running-7.1.3 test
Welcome to psql 8.0.0rc5, the Postgre
This doesn't happen on a fresh initdb. In fact, it doesn't happen even
directly after I load data. It might take a day or two, but eventually
the problem manifests itself. I can reproduce it 100% of the time now.
I've noticed this on 8rc1-5. Josh and I will get you a gdb trace ASAP.
Daniel
To
"Geert Jansen" <[EMAIL PROTECTED]> writes:
> I'm running PostgreSQL 7.4.6 on RHEL 4 Beta 2. There seems to be a
> bug, or call it inconsistentcy with the documentation, in the
> interval data type. According to
> http://www.postgresql.org/docs/7.4/static/datatype-datetime.html, the
> resolution of
Dave Bodenstab <[EMAIL PROTECTED]> writes:
> I built 8.0.0rc5 on FreeBSD 4.8. It built with no errors. I then
> tried psql using another host running postgresql 7.1.3 and I get the
> goofy error message shown below.
psql's backslash commands are only guaranteed to work with a server of
the same
amorati <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE FUNCTION "public"."DisparadorHijoBorradoCMin1" ()
> RETURNS trigger AS
> ...
> LANGUAGE 'plpgsql' IMMUTABLE CALLED ON NULL INPUT SECURITY INVOKER;
> The problem is that the row's count done by the trigger is the same
> number of rows that a
>The following bug has been logged online:
>
>Bug reference: 1403
>Logged by: Phil
>Email address: [EMAIL PROTECTED]
>PostgreSQL version: 8
>Operating system: windows
>Description:Failed to create process: 2
>Details:
>
>Running the msi installer gave thie above messag
On Mon, Jan 17, 2005 at 12:36:33PM -0800, Kanu Patel wrote:
> I had an employee table with the following columns in it: id, name, address,
> phone, payinfo.
> I had loaded the data using: "copy employee from 'employee.txt';" command.
> I want to get namde of one employee, so I have entered the fo
On Sat, 15 Jan 2005, raxfar wrote:
>
> Bug reference: 1402
> PostgreSQL version: 8.0.0-rc2
> Description:getPrecision don't work
>
> java.sql.ResultSetMetaData _oMetaData.getPrecision(i)
> java.sql.ResultSetMetaData _oMetaData.getScale(i)
> methods not to get Precision and Scale
>
raxfar wrote:
The following bug has been logged online:
Bug reference: 1402
Logged by: raxfar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0-rc2
Operating system: windows 2000
Description:getPrecision don't work
Details:
have
java.sql.ResultSetMetaData _oM
Hi,
This kind of issue came, when i am porting the MySQL queries to
PostGreSQL. Here is the query in MySQL, it does not give syntax error,
whereas PGSQL errors.
Simplified form:
mysql> select (if (locate('/','iprange')=0,0,INET_ATON('iprange')));
+---
25 matches
Mail list logo