| From: | "David Wall" <d(dot)wall(at)computer(dot)org> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org>, <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: Vacuum analyze in 7.1.1 |
| Date: | 2001-06-14 04:16:24 |
| Message-ID: | 01b401c0f488$c684dea0$5a2b7ad8@expertrade.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
> I'll have to see if JDBC does an unlink anywhere.
Whoa! Looks like JDBC (as makes sense if you think about the libraries)
doesn't unlink those large objects. There is a call in the
postgresql-specific for doing the lo_unlink, but it requires an OID, and
when deleting a row, most of the time I only know the primary key, not the
OIDs inside. So, I guess I'll have to run vacuumlo from contrib before I do
the regular vacuum.
Does anybody know if vacuumlo is truly safe to use? I just ran it on my
test system and it removed a bunch of orphans, but I just hope they were
really orphans!
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Miles | 2001-06-14 04:23:56 | Re: problem connecting from another host |
| Previous Message | David Wall | 2001-06-14 04:15:28 | Re: Vacuum analyze in 7.1.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2001-06-14 06:27:06 | Error handling in ODBC |
| Previous Message | David Wall | 2001-06-14 04:15:28 | Re: Vacuum analyze in 7.1.1 |