Search Postgresql Archives

General Postgres performance tips when using ARRAY

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: pgsql-general@xxxxxxxxxxxxxx
Subject: General Postgres performance tips when using ARRAY
From: bubba postgres <bubba.postgres@xxxxxxxxx>
Date: Wed, 25 May 2011 18:17:26 -0700

So, what are the gotcha's around manipulating Arrays in stored procs?
It seems reasonable that an array_cat /etc would cause the creation of a new array, but does mutating an existing array also create a copy?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: General Postgres performance tips when using ARRAY
  - From: Merlin Moncure

Prev by Date: Re: Access to postgres conversion
Next by Date: Re: General Postgres performance tips when using ARRAY
Previous by thread: Access to postgres conversion
Next by thread: Re: General Postgres performance tips when using ARRAY
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux