Hi all!
Some time back I discussed the inclusion of replication (e.g.
postgres-R) into postgres.
One of the technical reasons that I understand against such a move is
the application dependence of replication. PostgresR requires a large
amount of code change in postgres.
All this leads to a bitter
Some time back I discussed the inclusion of replication (e.g.
postgres-R) into postgres.
One of the technical reasons that I understand against such a move is
the application dependence of replication. PostgresR requires a large
amount of code change in postgres.
All this leads to a bitter taste
On Mon, 2 Aug 2004, chinni wrote:
Is the core Postgres team thinking of providing such an API?
Would they be inclined to do so in the future?
Finally, in case they are not, would the postgres team be willing to
help independent contributors (like me) to standardize such an API and
accept the
On Mon, 2004-08-02 at 08:51, chinni wrote:
Hi all!
Some time back I discussed the inclusion of replication (e.g.
postgres-R) into postgres.
One of the technical reasons that I understand against such a move is
the application dependence of replication. PostgresR requires a large
amount of
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 2 Aug 2004, chinni wrote:
Is the core Postgres team thinking of providing such an API?
the only worry I'd have is a new one
coming along that needs to plug in at a different point in the server ...
That would be the major worry I'd have.
