Kris Jurka <[EMAIL PROTECTED]> writes:
> The below code creates overloaded
> functions that do not produce this error when called with a NULL argument.
> jurka=# CREATE FUNCTION g(int) RETURNS int AS 'SELECT 1;' LANGUAGE sql;
> CREATE FUNCTION
> jurka=# CREATE FUNCTION g(float) RETURNS int AS 'SE
I thought all ambiguous function calls would generate an error:
ERROR: function g("unknown") is not unique
HINT: Could not choose a best candidate function. You may need to add
explicit type casts.
but this doesn't seem to be the case. The below code creates overloaded
functions that do not
"Mike G." <[EMAIL PROTECTED]> writes:
> create a table with a data type of varchar (50) and name it email
> insert into this table the following values:
> [EMAIL PROTECTED]
> Execute the following statement:
> SELECT CASE WHEN count(substring(email FROM '@.')) > 0 THEN count(substring(email
> F
To reproduce:
create a table with a data type of varchar (50) and name it email
insert into this table the following values:
[EMAIL PROTECTED]
Execute the following statement:
SELECT CASE WHEN count(substring(email FROM '@.')) > 0 THEN count(substring(email FROM
'@.')) ELSE 0 END, email FROM y
"Reuven M. Lerner" <[EMAIL PROTECTED]> writes:
> /test/regress/./tmp_check/data/base/1 ... FATAL: could not create
> shared memory
> segment: Cannot allocate memory
> DETAIL: Failed system call was shmget(key=2, size=1163264, 03600).
OS X has an unreasonably small limit on shared memory size;
Hi,
It seems to me that
a bug was introduced in 8.0 version.
I'm using Beta3
version on WIN32 platform.
CREATE OR REPLACE
FUNCTION TEST( ) RETURNS int4 AS '
BEGIN
<>LOOP Raise Notice ''Loop
1'';
Hi guys,
Following up on the bug I posted the other day about incorrect
timestamps, the FreeBSD team are wondering if it might be caused by
conflicting PostgreSQL instances in different FreeBSD jails on the same
host machine.
However, we've noticed no other problems with this configuration over
I just downloaded and compiled PostgreSQL 8.0 beta 3. The directory and
files are all owned by the "postgres" user, and I compiled as that
user. I configured with:
./configure --prefix=/sw --with-tcl --with-python --with-libs=/sw/lib/
--with-includes=/sw/include/
(/sw is the root of the "fi
PostgreSQL Bugs List wrote:
The following bug has been logged online:
Bug reference: 1284
Logged by: Shilpa Upadhye
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Redhat Linux 9.0
Description:The backend has broken the connection.
Deta
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> We are getting the following error:
> The backend has broken the connection. Possibly the action you have
> attempted has caused it to close.
The information you've provided is quite useless for resolving a
server-side problem :-(. What query
The following bug has been logged online:
Bug reference: 1284
Logged by: Shilpa Upadhye
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Redhat Linux 9.0
Description:The backend has broken the connection.
Details:
Hi,
We have po
11 matches
Mail list logo