How do I view the arguments and details of a user defined function?
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi,
I have to pass a set of values and arrays in postgresql 8.2 functions. But I
am not getting any help on that. Please let me know if any one has idea.
Thanks,
Jyoti
:25 PM
To: Jyoti Seth
Cc: pgsql-general@postgresql.org; [EMAIL PROTECTED]
Subject: Re: [SQL] setof or array as input parameter to postgresql 8.2
functions
Hello
maybe:
create function foo(varchar[][]) returns void as $$ begin end$$
language plpgsql;
postgres=# select foo(array[array[1,2], array
Thanks a lot.
Regards,
Jyoti
-Original Message-
From: Pavel Stehule [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 14, 2007 11:27 AM
To: Jyoti Seth
Cc: pgsql-general@postgresql.org; [EMAIL PROTECTED]
Subject: Re: [SQL] setof or array as input parameter to postgresql 8.2
functions
2007
physical clustering, or without? i.e. do i need to run a
cluster command immediately after the restore, or is it already done?
Thanks,
Seth
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Yaroslav Tykhiy wrote:
By the way, `chkdsk' in Windows or `fsck' in Unix can, in a way, be a
_source_ of file loss if the file metadata got damaged badly, e.g., by a
system crash, and the file node has to be cleared. So I've always been
curious if there is a way to retrieve surviving records f
Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:
tracedb=> \d webdata
Table= webdata
+--+--+---+
| Field |
This may be a newbie question, but according to the 7.4 docs, an ACCESS
EXCLUSIVE lock is only acquired by the ALTER TABLE, DROP TABLE,
REINDEX, CLUSTER, and VACUUM FULL commands.
However, when viewing pg_locks during the execution of a stored
procedure that does not perform any of the above comma
For anyone that is interested, my problem was solved on another list.
Turns out the TRUNCATE command that I run at the beginning of the SP
creates and holds an access exclusive lock on the table for the entire
duration of the SP. I changed it to DELETE FROM and my problem was
fixed.
Full discussi