Jean-Paul ARGUDO wrote:
> > I've attached an updated version of Karel Zak's pg_qcache patch, which
> > adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> > statements).
>
> Woah :-))
>
> Thanks Neil! You may be remind of a thread in february, where I talked
> about a survey abo
> I've attached an updated version of Karel Zak's pg_qcache patch, which
> adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> statements).
Woah :-))
Thanks Neil! You may be remind of a thread in february, where I talked
about a survey about migrating from Oracle 8.0 / NT4 to Po
On Sun, 14 Apr 2002 22:39:32 +0200
"Karel Zak" <[EMAIL PROTECTED]> wrote:
> - PREPARE_KEY_PREFIX_SIZE is 4 not 3
>
> - in the PrepareKey() is needful fix:
>
>
> + if (store == PREPARE_STORE_SHARE) { /* shared between same DB */
> + *flag |= QCF_SHARE_NOTREMOVEABLE;
> +
On Sun, Apr 14, 2002 at 10:13:17PM +0200, Karel Zak wrote:
> > (2) Sometimes executing a PREPARE gives this warning:
> >
> > nconway=> prepare q1 as select * from pg_class;
> > WARNING: AllocSetFree: detected write past chunk end in TransactionCommandContext
>0x83087ac
> > PREPARE
> >
> > Do
On Sat, Apr 13, 2002 at 06:47:32PM -0400, Neil Conway wrote:
>
> I've attached an updated version of Karel Zak's pg_qcache patch, which
> adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> statements). It should apply cleanly against CVS HEAD, and compile
> properly -- beyond tha
Neil Conway wrote:
> Hi all,
>
> I've attached an updated version of Karel Zak's pg_qcache patch, which
> adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> statements). It should apply cleanly against CVS HEAD, and compile
> properly -- beyond that, cross your fingers :-)
I wan
> Just explicitly prepared ones. Caching all queries opens a can of
> worms that I'd rather not deal with at the moment (volunteers to
> tackle this problem are welcome).
I definitely agree. I think that the optimisation possiblities offered to
the DBA for shared prepared statements are quite la
On Sun, 14 Apr 2002 12:11:31 +0800
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> wrote:
> Does it cache all queries or just explicitly prepared ones?
Just explicitly prepared ones. Caching all queries opens a can of
worms that I'd rather not deal with at the moment (volunteers to
tackle this prob
ent: Sunday, April 14, 2002 6:47 AM
Subject: [HACKERS] experimental pg_qcache patch
> Hi all,
>
> I've attached an updated version of Karel Zak's pg_qcache patch, which
> adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> statements). It should apply cleanl
ent: Sunday, April 14, 2002 6:47 AM
Subject: [HACKERS] experimental pg_qcache patch
> Hi all,
>
> I've attached an updated version of Karel Zak's pg_qcache patch, which
> adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
> statements). It should apply cleanl
Hi all,
I've attached an updated version of Karel Zak's pg_qcache patch, which
adds PREPARE/EXECUTE support to PostgreSQL (allowing prepared SQL
statements). It should apply cleanly against CVS HEAD, and compile
properly -- beyond that, cross your fingers :-)
Please take a look at the code, play
11 matches
Mail list logo
