Re: [Postgres-xc-general] PostgreSQL-XC: error in README?

[Michael P. <mic...@gm...>]

On Mon, Jun 11, 2012 at 9:13 PM, Fernando Lozano <fer...@lo...>wrote:

>  Hi Michael,
>
> Found the offending text. It's in the README from many releases, including
> 1.0.0:
>
> Postgres-XC is aiming to provide transparent access to the database, which
> means one can use existing PostgreSQL application as is. For implementation
> reason,
> ***transparency level is limited to access via libpq libraries***
> and simple statements as found in the Architecture Document in the release
> material.
>
> PHP, Perl and most users won't be bothered because those language drivers
> use libpq, but Java developers use a pure-java JDBC driver which does not
> uses libpq at all.
>
> This statement on the README may be understood as "there are changes to
> libpq in postgresql-xc so you have to use our libpq. Other clients won't
> work".
>
The point is that we haven't changed libpq at all. It is exactly the same
as vanilla postgres.


>
> But as I understand you reply, I can use any libpq to access postgresql-xc
> without problem. For example, a pgAdminIII binary for windows that I
> already use for a plain PostgreSQL server should work out-of-the-box with
> PostgreSQL-XC, or the rpm files from Debian Linux for a PHP app. And I
> could also use other clients, not based on libpq, such as a JDBC driver
> anda a .Net provider, right?
>
Yes everything should work.
I played a couple of months ago and pgadmin was working correctly by
connecting to Coordinator.
Other drivers also should work normally. If they do not work, well it is a
bug. As I told before there are only limitations with odbc, because it uses
ctid and in XC ctid is not unique among nodes.

Btw, I found that the incorrect file is in the README of each version
folder in SourceForge.
Thanks for pointing that out. I'll upload a modified version.
-- 
Michael Paquier
http://michael.otacoo.com