3) How does one get the $PGDATA directory?
DataDir. Why should you care? An index AM that wants to know this is probably broken IMHO; it's certainly trying to do something that's outside the charter of index AMs, and is likely to cause lots of headaches.
Xapian has it's own storage subsystem, and that's what I'm using to store the index... not using anything internal to postgres (although this could change). As such, Xapian needs to know *where* to save its indexes... $PGDATA seemed like a good place to start.
4) Can a function be registered as part of a transaction, pre-commit --
so the function can have an opportunity to abort the transaction.
Why would that be a good idea? When exactly would you expect it to be
called (relative to the other ninety-nine things that happen at commit)?
How are you going to recover if something else aborts the transaction,
either before or after your function runs?
I don't really have an answer to this. :)
I get the impression from your questions that you are trying to make an end run around the transaction mechanism.
Perhaps. I'm actually fishing for ideas to bridge xapian's transaction facilities to postgres. Your comment confirms my suspicions that it just ain't gunna work out.
This is almost certainly doomed to failure. You need to find a way of storing all your data
within the ordinary index structure.
You are probably right. :) I'm just playing around right now. I do appreciate your response, it's given me a lot to think about.
eric
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
