On Fri, Aug 24, 2012 at 4:11 PM, Artur Zając wrote:
>>> I would like to create some application using triggers and
>>> LISTEN/NOTIFY framework. I've tested it, and I noticed that
>>> performance of NOTIFY significally decreases with increasing number of
>>> distinct NOTIFIES in transaction.
>>> I
On Tue, Aug 28, 2012 at 2:11 AM, Pavan Deolasee
wrote:
>
>
> On Mon, Aug 27, 2012 at 6:07 PM, Jayadevan M
> wrote:
>>
>> Hello all,
>>
>> I have a plpgsql function that takes a few seconds (less than 5) when
>> executed from psql. The same function, when invoked from java via a
>> prepared state
On Tue, Aug 28, 2012 at 2:39 AM, Mathieu De Zutter wrote:
> Hi all,
>
> I've been trying to apply pg_tgrm for the search-function of my application.
> The database fits a few times in the available RAM, and is mostly read-only.
> Plans, schema and configs in attachment. Postgresql version 9.1.4 on
On Tue, Aug 28, 2012 at 1:57 AM, Daniel Farina wrote:
> My database has taken many days (over a week) to stabilize. I was
> about to write that it never stops growing (we'd eventually have to
> VACUUM FULL or do a column rotation), but that is not true. This
> graph is a bit spotty for unrelated
On Mon, Aug 27, 2012 at 11:24 PM, Liron Shiri wrote:
> There were no "hot standby" configuration, but the DB has start grow fast
> after restoring from a base backup as described in
> http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-BASE-BACKUP
Very interesting. That
Hi all,
I've been trying to apply pg_tgrm for the search-function of my
application. The database fits a few times in the available RAM, and is
mostly read-only.
Plans, schema and configs in attachment. Postgresql version 9.1.4 on Debian.
When just searching in one table, it behaves perfectly her
On Mon, Aug 27, 2012 at 6:07 PM, Jayadevan M
wrote:
> Hello all,
>
> I have a plpgsql function that takes a few seconds (less than 5) when
> executed from psql. The same function, when invoked from java via a
> prepared statement takes a few minutes. There are a few queries in the
> function. Out
