I wrote:
> "Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
>> CREATE OR REPLACE FUNCTION gregtest(int) RETURNS varchar
>> LANGUAGE sql AS $$ SELECT 'abc'::text; $$;
> Hm, I'd argue that that should be rejected. SQL functions currently
> demand exact match between the declared return type and th
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE FUNCTION gregtest(int) RETURNS varchar
> LANGUAGE sql AS $$ SELECT 'abc'::text; $$;
Hm, I'd argue that that should be rejected. SQL functions currently
demand exact match between the declared return type and their final
SELECT
The following bug has been logged online:
Bug reference: 3116
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.8
Operating system: Linux
Description:attribute has wrong type
Details:
Reproduced on 8.2.3, 8.1.8, and CVS HEAD:
C
Bryan O'Neill wrote:
PostgreSQL version: 7.2.3
That's a very old and unsupported version. You should upgrade,
regardless of this problem.
Operating system: Redhat 8.0
Description:backend died abnormally HELP!!
Details:
On 3/4/07, I received the following message from the subje
"Jarrod Chesney" <[EMAIL PROTECTED]> writes:
> The "-L, --use-list=FILENAME use specified table of contents for ordering"
> flag does nothing in pg_restore in linux.
Fairly hard to believe. Please provide a reproducible example...
regards, tom lane
-
"Randy Isbell" <[EMAIL PROTECTED]> writes:
> When restoring the output of an online backup, many tables now have
> duplicate OID values / primary keys, viz:
> ...
> sn=# reindex table at_dns;
> ERROR: could not create unique index
I'm confused. You're claiming that the reload succeeds, but after
On Sun, 4 Mar 2007, Valery Meshkov wrote:
The following bug has been logged online:
Bug reference: 3106
PostgreSQL version: 8.2.3
Description:A problem with escaping table name pattern for
DatabaseMetaData.getColumns()
Details:
I am seeing a problem in the JDBC driver postgresql
Hello,We have a Postgresql 8.1.8 and a problem, probably no bug.But we must go in production tomorrow and we don't know where to look to solve this. Therefore I hope somebody can help us.The problem is when we insert with a function, we get the message SQLSTATE = 25P02Error while executing the quer
The following bug has been logged online:
Bug reference: 3115
Logged by: Bryan O'Neill
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.2.3
Operating system: Redhat 8.0
Description:backend died abnormally HELP!!
Details:
On 3/4/07, I received the following me
The following bug has been logged online:
Bug reference: 3106
Logged by: Valery Meshkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Windows
Description:A problem with escaping table name pattern for
DatabaseMetaData.getColumns()
Detail
The following bug has been logged online:
Bug reference: 3113
Logged by: Jarrod Chesney
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Linux 2.6.17.10 Ubuntu (Edgy Edge)
Description:pg_restore --use-list=FILENAME
Details:
In pg_restore.
The following bug has been logged online:
Bug reference: 3111
Logged by: Bruno
Email address: [EMAIL PROTECTED]
PostgreSQL version: v8.2.3
Operating system: Win2003 Server 64bits
Description:PostgreSQL Driver is compatible with Win2003 Server 64
bits?
Details:
Hello
The following bug has been logged online:
Bug reference: 3110
Logged by: Randy Isbell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: FreeBSD 6.1 i386
Description:Online Backup introduces Duplicate OIDs
Details:
This issue is observed in
Theodore Petrosky wrote:
I tried to upload to the list but I think the file got
lost...I am attaching it here.
A-ha, this is the problem:
! psql: FATAL: sorry, too many clients already
I'm guessing this is the same issue as here:
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01821.
14 matches
Mail list logo