Re: [PATCHES] - WIP Patch Updatable Cursor

From: "John Bartlett" <johnb(at)fast(dot)fujitsu(dot)com(dot)au>
To: "'Gavin Sherry'" <swm(at)alcove(dot)com(dot)au>
Cc: <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org>, "'Heikki Linnakangas'" <heikki(at)enterprisedb(dot)com>
Subject: Re: [PATCHES] - WIP Patch Updatable Cursor
Date: 2007-03-02 06:47:46
Message-ID: !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA/w1P36NVXkuUGCDGiycCfMKAAAAQAAAADPOlSx7DTEirLCUebrOeSAEAAAAA@fast.fujitsu.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Hi Gavin,

Thanks for your comments.

I shall set up the ctids list to be stored in memory initially and dump to a
temp file if needed.

Regards,
John Bartlett

-----Original Message-----
From: pgsql-patches-owner(at)postgresql(dot)org
[mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Gavin Sherry
Sent: Wednesday, 28 February 2007 3:23 PM
To: John Bartlett
Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-patches(at)postgresql(dot)org; 'Heikki
Linnakangas'
Subject: Re: [HACKERS] [PATCHES] - WIP Patch Updatable Cursor

On Wed, 28 Feb 2007, John Bartlett wrote:

> Hi,
>
> A list of ctids is stored in the file.

I would have thought these would be stored in memory. If the set got
large, you'd use a temporary file the way other systems which overflow to
disk do?

>
> The file is used to store the ctids during an updatable cursor
transaction.
>
> It is set up as a permanent file as it has a potential lifetime of
> preserving data between crashes of the backend. Temporary files tend to be
> used for data that is defined within a single command. In this case the
file
> needs to exist within a transaction and across backend processes.

It does not. Cursors are implicitly closed when a session is closed. A
backend crash or system restart closes all open sessions.

>
> The file gram.y has been corrected in my version.
>
> The files ctidListStore.c and ctidListStore.h were pasted into the patch
> file, as the diff -N command produced a file of several hundred thousand
> lines.

Edit the file with a text editor. If you know which files should be
excluded (like tags files), use diff --exclude=<pattern>.

Thanks,

Gavin

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly

This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN 27 003 693 481. It is confidential to the ordinary user of the email address to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you.

If you do not wish to receive commercial email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe(at)fast(dot)fujitsu(dot)com(dot)au

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2007-03-02 07:01:00 Re: HOT - preliminary results
Previous Message Tatsuo Ishii 2007-03-02 06:06:39 Re: broken doc

Browse pgsql-patches by date

  From Date Subject
Next Message Patric Bechtel 2007-03-02 07:10:47 Re: Numeric patch to add special-case representations for < 8 bytes
Previous Message Tom Lane 2007-03-02 06:38:11 Re: Numeric patch to add special-case representations for < 8 bytes