Re: Review: query result history in psql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review: query result history in psql
Date: 2013-07-01 11:05:13
Message-ID: CAFj8pRBh0dMZaJjHrYbrTKyggJa3KfuWCYHjbLVULp2=OOvxrA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/7/1 Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>:
>
>> When I tested this feature, I had 30 caches per 5 minutes, and only a
>> few from these queries had a sense. Switch between off and on is not
>> user friendly. I believe so there can be other solution than mine, but
>> a possibility to friendly clean unwanted caches is necessary.
>
>
> If you know that you'll need the result of a query beforehand, you can
> always use SELECT ... INTO ... . No client-side features required.
>
> This feature is intended for people running plenty of ad-hoc queries, when
> every result could potentially be useful.
>

a idea is good, but I don't think, it can be useful with current
implementation. How I can identify, what is correct answer for my
query? Have I remember twenty numbers and twenty queries?

Regards

Pavel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message KONDO Mitsumasa 2013-07-01 11:29:50 Re: [PATCH] add --progress option to pgbench (submission 3)
Previous Message Maciej Gajewski 2013-07-01 11:01:01 Re: Review: query result history in psql