Re: Review: query result history in psql - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Review: query result history in psql
Date
Msg-id CAFj8pRBh0dMZaJjHrYbrTKyggJa3KfuWCYHjbLVULp2=OOvxrA@mail.gmail.com
Whole thread Raw
In response to Re: Review: query result history in psql  (Maciej Gajewski <maciej.gajewski0@gmail.com>)
Responses Re: Review: query result history in psql
List pgsql-hackers
2013/7/1 Maciej Gajewski <maciej.gajewski0@gmail.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



pgsql-hackers by date:

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