| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | Jerry Robertson <jrrobert(at)rgid(dot)net>, <scrappy(at)postgresql(dot)org>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Question |
| Date: | 2004-04-27 21:43:31 |
| Message-ID: | 87zn8xyu4c.fsf@asmodeus.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> When postgresql "deletes" a tuple prior to it being vacuumed, it simply
> sets a time stamp on it that vacuum can use to see it is "deleted" and no
> longer visible. If you are actually getting back tuples with the words
> #Deleted in them, then I would guess you have an application error.
The application in question is almost certainly Microsoft Access--it
has its own weird idea of how to track deleted rows in an ODBC table.
The '#Deleted' phenomenon with Access is fairly common and well
documented.
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rory Campbell-Lange | 2004-04-27 22:40:37 | Re: PL/SQL question |
| Previous Message | scott.marlowe | 2004-04-27 20:49:13 | Re: Question |