Re: lo_truncate

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: lo_truncate
Date: 2007-03-01 02:10:17
Message-ID: 200703010210.l212AHe02306@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---------------------------------------------------------------------------

Kris Jurka wrote:
>
> The attached patch implements lo_truncate for truncating large objects to
> a given length. This is required for implementing Blob.truncate in the
> JDBC driver[1] and rounds out filesystem like functionality for large
> objects.
>
> Kris Jurka
>
> [1] http://java.sun.com/javase/6/docs/api/java/sql/Blob.html#truncate(long)
Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-03-01 02:11:45 Re: xpath_array with namespaces support
Previous Message Bruce Momjian 2007-03-01 02:09:16 Re: Fast COPY after TRUNCATE bug and fix