Mark Gibson <[EMAIL PROTECTED]> writes:
I have an idea, to break pg_dump into functions within PostgreSQL.
Philip Warner wrote:
However, there are some complications because pg_dump is also the
upgrade tool; the backed can only know how to describe itself for the
current dialect of SQL accepted b
ot;Christopher Kings-Lynne" <[EMAIL PROTECTED]>
To: "Mark Gibson" <[EMAIL PROTECTED]>
Cc: "Hackers (PostgreSQL)" <[EMAIL PROTECTED]>
Sent: Tuesday, September 14, 2004 10:44 AM
Subject: Re: [HACKERS] pg_dump as a bunch of PostgreSQL functions
> &g
Mark Gibson <[EMAIL PROTECTED]> writes:
> I have an idea, to break pg_dump into functions within PostgreSQL.
This strikes me as largely useless, because the problems that are
actually hard for pg_dump are not at the level of individual objects;
they have to do with problems like determining a saf
At 06:00 PM 14/09/2004, Mark Gibson wrote:
I have an idea, to break pg_dump into functions within PostgreSQL.
This has been suggested before, and I think been generally accepted as the
right broad approach (the basic idea that the pg backend should know how to
describe itself).
Recent versions o
Would this be practical, would it be possible to break the pg_dump
code out into PostgreSQL functions?
Anyone have any ideas/thoughts/suggestions on this?
It's been my plan for sometime, I'm time-starved at the moment however.
Chris
---(end of broadcast)-
Hello folks,
I have an idea, to break pg_dump into functions within PostgreSQL.
We currently have some functions like pg_get_viewdef, but it would
be great to have a function or functions to dump the SQL definition
of any object.
This would allow easy dumping of any object from admin interfaces,
an
