From: Christopher Kings-L. <ch...@fa...> - 2003-12-21 10:34:18
|
> I think the same goes for nix users as well, since I have a couple of setups > where I don't have a pg_dump accessible for this functionality. In those > cases a basic table dumping feature is really handy. Thing is, I know how broken the dumps really are. If anyone is actually relying on them 100% they're kind of in trouble. eg: * Absolutely no inheritance support (it's incredibly complex) * No SETVAL() at the bottom * Poor efficiency caused by trying to support all versions of postgres (eg. all indexes and constraints created first) At the moment, I'm making it so that if you have pg_dump installed you get pg_dump dumps, otherwise it falls back to ours. However, I would really like to rip it out entirely - it's just too much work to maintain, etc. How are you in a situation where you have libpq installed on a unix machine, but not pg_dump? Seriously, how common is this situation? Chris |