pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Wall <d.wall@computer.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Vacuum analyze in 7.1.1
Date: Wed, 13 Jun 2001 21:01:08 -0700
Message-ID: <016901c0f486$a6372240$5a2b7ad8@expertrade.com> (raw)
References: <00c401c0f43b$a5423000$5a2b7ad8@expertrade.com>
	<3101.992468005@sss.pgh.pa.us>
	<006501c0f45b$eca1c580$5a2b7ad8@expertrade.com>
	<15660.992481431@sss.pgh.pa.us>

The new vacuum comments are much more clear.  Bravo.

As for the large objects, I'll have to see what happens when I delete a row
that contains a large object.  Sounds like they are not being deleted for me
as I had thought.  That's too bad since I know it must be a common problem
for those who use them.  I use the JDBC library, so I don't really even
create the large objects except through standard JDBC calls like
PreparedStatement.setBytes().  I'll have to see if JDBC does an unlink
anywhere.

David




view thread (8+ messages)  latest in thread

Message-ID: <016901c0f486$a6372240$5a2b7ad8@expertrade.com>
Permalink:  ../016901c0f486$a6372240$5a2b7ad8@expertrade.com/
Also on:    postgresql.org/message-id/016901c0f486$a6372240$5a2b7ad8@expertrade.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: d.wall@computer.org, tgl@sss.pgh.pa.us, pgsql-general@postgresql.org
  Subject: Re: Vacuum analyze in 7.1.1
  In-Reply-To: <016901c0f486$a6372240$5a2b7ad8@expertrade.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox