From section 15.4 of the manual:
"If you are upgrading from PostgreSQL "9.0.x", the new version can use
your current data files so you should skip the backup and restore steps"
Is 9.0beta4 considered a 9.0.x version, or do I need to backup/restore
when upgrading from that version?
Thanks
sql. Try, plperl or some synamic PL language, please
>
> regards
> Pavel Stehule
>
> > On Tue, Feb 10, 2009 at 1:22 PM, Tom Lane wrote:
> >>
> >> Lee Hughes writes:
> >> > Trying to figure out how to reference a field in a cursor result, or
> in
>
I thought that's what EXECUTE was for in plpgsql -- isn't there a way to
extract the value of a field in a row/record variable by building a SELECT
string and passing it to EXECUTE?
On Tue, Feb 10, 2009 at 1:22 PM, Tom Lane wrote:
> Lee Hughes writes:
> > Trying to figure o
Trying to figure out how to reference a field in a cursor result, or in a
row/record variable that I've FETCHed the cursor into, where the target
field name is in a variable or parameter. I think I'm just missing the
dereferencing syntax. I've studied the manual and tried using EXECUTE to no
avail.
:
> Lee Hughes writes:
> > Hi, I need a function that accepts a table name and returns a
> 2-dimensional
> > array of the table data.
>
> Well, in 8.3 and up there are arrays of composite types, so you can
> do something like
>
>select array(select m
Hi, I need a function that accepts a table name and returns a 2-dimensional
array of the table data.
I found some related posts on this and other forums and tried several
approaches with plpgsql but have had no success.
I know I can pull the table data out to the application tier and transform
it
