Here's a major issue. Since converting over to PostgreSQL, a new thing is happening. If I delete a comment, normally the deletion process takes you back to the edit screen for the entry the comment was on, so that you can rebuild the entry. Problem is, now, under PostgreSQL, when it takes you to the entry edit screen after deleting the comment... the ENTRY IS GONE, and is replaced by the text of the deleted comment.

Now this, this would be a good thing to have a fix for.

are you using safari? this may be the infamous safari bug.

Ah, that's very possible. Next time I delete a comment, I'll try Moz Firebird.

In the meantime, tho, I'm not clear on whether or not to use Mt Blacklist's "delete comment and rebuild entry" feature when comment spam hits. Presumably, it would be okay, since that's got nothing to do with form field names on a webpage, but I don't think I want to test that and end up killing an entry.

Although, I should say that this was not occuring prior to my switching to PostregSQL. Under Berkeley, deleting comments worked just fine.

What you're describing definitely sounds like the Safari bug, not a database issue.

You could try posting a test entry, posting a comment, and use MTBlacklist to delete it. Thus, no risk to an entry you don't want to lose.

If it were a Safari issue, would it not have manifested itself prior to switching to PostgreSQL? There's no reason for it to have cropped up now and not prior to two days ago unless it's somehow a database issue.

I don't dispute the existence of the Safari issue, just it's applicability to this issue. Why would a Safari issue only just now arise?

I can't answer that, because I use neither Safari nor PostgreSQL. I know the bug exists, but I don't know that it happens every single time a comment is deleted. I just know that the behavior has been reported here often enough to where we now recognize "the Safari bug" when we hear about it.

Aside from that, I'd find it unusual to see a database bug cause the exact problem that the Safari bug has been reputed to cause for a while now - especially if you're using Safari and not some other browser. That's seems like a highly unlikely coincidence to me - a heretofore Safari-only bug suddenly starts to occur in conjunction with a switch to PostgreSQL? That's not a commonly used database from what I've seen here on the forum, but I guess we could go back and survey those Safari users who have experienced the bug to see what database they're using. Maybe we've been giving Safari a bad rep by pinning the blame on it unfairly.

Have you experienced the same thing in a different browser? If so, then I'm more inclined to believe that this is more than just mere coincidence, and we'll need to make note of it for the future users who may run into the same type of problem.

Deleting through MT-Blacklist is still safe.

To work around the bug (safari or not), after you delete the comment and its text shows up in the entry body, hit apple-L (location) and then enter. This will reload the page. If the entry reappears, then it is indeed the safari bug.