"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> it can by more simple than I though. I need only one flag, and if its true
> then I don't create language variables for OUT params. But I need one next
> column in pg_proc.
I thought you said this was just syntactic sugar for capabilities we
already had?
> Currently a lot of columns in pg_proc is bool. What about one binary columns
> for other options? I hope so next versions can support autonomous
> transaction, which need flag too.
I think stored procedures of that sort aren't functions at all, and
probably don't belong in pg_proc.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
