postgres-xc-developers Mailing List for Postgres-XC (Page 2)

On 2012/05/25, at 15:54, MOHD ARSHAD SALEEM <mar...@ta...> wrote:

> Hi team,
> 
> I wanted to know while running following commands->
>  initdb -D /usr/local/pgsql/data/
> 
> Showing following error->1. initdb: Postgres-XC node name is mandatory
>                                     2. Try "initdb --help" for more information.
> After getting this error i gave the username of where i installed postgres-XC.again error is same
I guess this is your first shot with Postgres-xc. Xc is a cluster, and option --nodename is a mandatory option specific to xc to initialize a node with a wanted node name.
This node name is used to identify uniquely this node in the cluster.

I have 2 suggestions:
1) documentation is published so you should definitely refer to it. For 1.0 it is here:
http://postgres-xc.sourceforge.net/docs/1_0/
2) install the sources like a normal Postgres with configure/make/make install and launch a simple cluster.
You can refer to the document called "start xc cluster in 10 commands" located here:
http://sourceforge.net/projects/postgres-xc/files/Publication/
Then test this cluster, it will help you understand the basics if xc.

Michael

Thanks to all for your quick reply

Regards
Arshad
________________________________________
From: koi...@gm... [koi...@gm...] on behalf of Koichi Suzuki [koi...@gm...]
Sent: Friday, May 25, 2012 11:51 AM
To: Pavan Deolasee
Cc: MOHD ARSHAD SALEEM; pos...@li...
Subject: Re: [Postgres-xc-developers] Query related to Postgres-XC

Thanks.   I added this to the feature request.
----------
Koichi Suzuki


2012/5/25 Pavan Deolasee <pav...@gm...>:
> On Fri, May 25, 2012 at 10:53 AM, Koichi Suzuki <koi...@gm...> wrote:
>> So far, officially not.
>
> I should add though that some of us have used 32-bit machines x86 for
> development of PGXC and haven't see any major issues. So that should
> give you some comfort if you want to deploy/try PGXC on 32-bit
> machines.
>
> Thanks,
> Pavan

HI Arshad,
Every node participating in the XC cluster is identified by a name.

initdb -D /usr/local/pgsql/data/ --nodename datanode_1 (or any node you
have given to this node)

On Fri, May 25, 2012 at 2:54 AM, MOHD ARSHAD SALEEM <
mar...@ta...> wrote:

>  Hi team,
>
> I wanted to know while running following commands->
>  initdb -D /usr/local/pgsql/data/
>
> Showing following error->1. initdb: Postgres-XC node name is mandatory
>                                     2. Try "initdb --help" for more
> information.
> After getting this error i gave the username of where i installed
> postgres-XC.again error is same
>
> Regards
> Arshad
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Suzuki-san,

Now we are developing XC's peripheral tools like as back-up, performance
observation, fail over cluster. While developing, the tool development
team would ask some questions to XC core developing team.

In such a cases, we (NTT people) used to placing questions with 'Qustion
application form' which includes version of the system in question,
environment information (OS name and its version, hardware
configuration), operation sequence and its results and so on. (In short,
I mean something like NTT's "Bug-hyo").
Because it is convenient for us to inform a reciever of things needed
completely and to manage each questions easily.

I was wondering if you could accept the questions placed with such an
application form and write answers with it.

Best regards,

Tetsuo Sakata.
-- 
sakata.tetsuo _at_ lab.ntt.co.jp
SAKATA, Tetsuo. Shinagawa Tokyo JAPAN.

Hi team,

I wanted to know while running following commands->
 initdb -D /usr/local/pgsql/data/

Showing following error->1. initdb: Postgres-XC node name is mandatory
                                    2. Try "initdb --help" for more information.
After getting this error i gave the username of where i installed postgres-XC.again error is same

Regards
Arshad

Thanks.   I added this to the feature request.
----------
Koichi Suzuki


2012/5/25 Pavan Deolasee <pav...@gm...>:
> On Fri, May 25, 2012 at 10:53 AM, Koichi Suzuki <koi...@gm...> wrote:
>> So far, officially not.
>
> I should add though that some of us have used 32-bit machines x86 for
> development of PGXC and haven't see any major issues. So that should
> give you some comfort if you want to deploy/try PGXC on 32-bit
> machines.
>
> Thanks,
> Pavan

Basically you can.
I also used both 32b and 64b with some clusters.

On 2012/05/25, at 13:46, MOHD ARSHAD SALEEM <mar...@ta...> wrote:

> Hi Team,
> 
> I wanted to know that Postgres-XC supported for 32 bit machine or not.
> 
> Regards
> Arshad
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

On Fri, May 25, 2012 at 10:53 AM, Koichi Suzuki <koi...@gm...> wrote:
> So far, officially not.

I should add though that some of us have used 32-bit machines x86 for
development of PGXC and haven't see any major issues. So that should
give you some comfort if you want to deploy/try PGXC on 32-bit
machines.

Thanks,
Pavan

So far, officially not.
----------
Koichi Suzuki


2012/5/25 MOHD ARSHAD SALEEM <mar...@ta...>:
> Hi Team,
>
> I wanted to know that Postgres-XC supported for 32 bit machine or not.
>
> Regards
> Arshad
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Hi Team,

I wanted to know that Postgres-XC supported for 32 bit machine or not.

Regards
Arshad

On Thu, May 24, 2012 at 7:06 PM, Ashutosh Bapat <
ash...@en...> wrote:

> Hi All,
> PFA the patch to fetch only the required columns from the datanode. Right
> now, we fetch all the columns of a table from datanode in many cases. Also
> modified test outputs which had diffs because of EXPLAIN output.
>
> I am expecting this patch to give a little performance improvement when a
> query is not FQSed, since the data fetched from the remote tables is
> reduced.
>
> Since this has not much impact on the code or regression, I would commit
> it only to master branch.
>
+1
This is a new feature and a planner improvement, so it can only be
committed in master.
1.0 stable will be used only to fix bugs. And under 1.0 the privilege
column problem was a limitation we decided to keep.

Btw, I haven't seen any problems with regressions, the test case join is
also going faster.
It might be interesting to do a measurement with that once committed.
-- 
Michael Paquier
http://michael.otacoo.com

> >    2) On Datanodes, autovacuum non-analyze processes did not fetch a
> global
> >    transaction ID from GTM and this transaction ID was not included in
> global
> >    snapshot. Hence, global data consistency and visibility was
> compromised
> >    on local nodes. This issue made autovacuum and pg_toast going crazy
> if the
> >    system was put under heavy load (transaction timeout occuring).
>
> As part of this second one, are we excluding it for global snapshots?
>
> We previously had an issue where an autovacuum may take a long time,
> holding the XID open, causing all snapshots cluster-wide to have a
> very low xmin value and performance would spike down because we had to
> do a lot more MVCC visibility checks.  These local vacuum XIDs are
> then added back locally to other snapshots that are sent for
> processing on this node only. Does this commit undo this and make XIDs
> appear in global snapshots again?
>
GXIDs of vacuum analyze are not included in snapshots. O nly the workers.
The issue was with vacuum WORKERS that did not begin a transaction on GTM,
so there transaction ID was not visible in snapshot and this was causing a
huge number of side-effects with data visibility.


> Just making sure we are not re-introducing this performance issue.  How
> many autovacuum workers were there?

Default max number = 3


> Does the original issue only happen when there is more than one?
>
Not sure. I unfortunately don't have that much time to do that many tests
but if someone still sees issues a report is always welcome.

With defaults, we made a 12h test and everything is stable now.
-- 
Michael Paquier
http://michael.otacoo.com

On Thu, May 24, 2012 at 4:38 AM, Michael Paquier
<mic...@us...> wrote:
> Project "Postgres-XC".
>
> The branch, REL1_0_STABLE has been updated
>       via  c9a15eeaaa78cf47f57830bbcb3234917e041afa (commit)
>      from  fcdf4ebba6613c7e7de2631325cf1ce682c684e4 (commit)
>
>
> - Log -----------------------------------------------------------------
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=c9a15eeaaa78cf47f57830bbcb3234917e041afa
>
> commit 39330d67e4c6a6a3ce8fe3abea1d60ca645ed1ff
> Author: Michael Paquier <mi...@ot...>
> Date:   Thu May 24 17:32:56 2012 +0900
>
>    Fix for bug 3525691: autovacuum process issue
>
>    This commit fixes 2 issues:
>    1) On Coordinator, autovacuum processes were using local snapshots
>    while it needs to fetch global snapshot data from GTM. This made several
>    PostgreSQL internal processes going mad with visibility like statistics or
>    catalogs in an environment using a lot of DDL.
>    2) On Datanodes, autovacuum non-analyze processes did not fetch a global
>    transaction ID from GTM and this transaction ID was not included in global
>    snapshot. Hence, global data consistency and visibility was compromised
>    on local nodes. This issue made autovacuum and pg_toast going crazy if the
>    system was put under heavy load (transaction timeout occuring).

As part of this second one, are we excluding it for global snapshots?

We previously had an issue where an autovacuum may take a long time,
holding the XID open, causing all snapshots cluster-wide to have a
very low xmin value and performance would spike down because we had to
do a lot more MVCC visibility checks.  These local vacuum XIDs are
then added back locally to other snapshots that are sent for
processing on this node only. Does this commit undo this and make XIDs
appear in global snapshots again?  Just making sure we are not
re-introducing this performance issue.  How many autovacuum workers
were there? Does the original issue only happen when there is more
than one?

>
>    It is believed that this bug is here since Postgres-XC 0.9.4, far before the
>    code was merged with PostgreSQL 9.1, and was causing numerous issues with
>    long and short-time runs.
>    For a reason I do not completely understand, this bug has become really easy
>    to reproduce since some race conditions in pg_toast code (tuptoaster.c) have
>    been fixed by Tom Lane in 9.1 stable.
>

Thanks,

Mason

On Thu, May 24, 2012 at 6:50 AM, Koichi Suzuki <ko...@in...>wrote:

> So in FQS we already have column projection?
>

FQS ships the whole query as it is, so it automatically fetches only
required data.


> ---
> Koichi
>
> On Thu, 24 May 2012 15:36:32 +0530
> Ashutosh Bapat <ash...@en...> wrote:
>
> > Hi All,
> > PFA the patch to fetch only the required columns from the datanode. Right
> > now, we fetch all the columns of a table from datanode in many cases.
> Also
> > modified test outputs which had diffs because of EXPLAIN output.
> >
> > I am expecting this patch to give a little performance improvement when a
> > query is not FQSed, since the data fetched from the remote tables is
> > reduced.
> >
> > Since this has not much impact on the code or regression, I would commit
> it
> > only to master branch.
> >
> > --
> > Best Wishes,
> > Ashutosh Bapat
> > EntepriseDB Corporation
> > The Enterprise Postgres Company
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

So in FQS we already have column projection?
---
Koichi

On Thu, 24 May 2012 15:36:32 +0530
Ashutosh Bapat <ash...@en...> wrote:

> Hi All,
> PFA the patch to fetch only the required columns from the datanode. Right
> now, we fetch all the columns of a table from datanode in many cases. Also
> modified test outputs which had diffs because of EXPLAIN output.
> 
> I am expecting this patch to give a little performance improvement when a
> query is not FQSed, since the data fetched from the remote tables is
> reduced.
> 
> Since this has not much impact on the code or regression, I would commit it
> only to master branch.
> 
> -- 
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Enterprise Postgres Company

On Fri, May 18, 2012 at 04:53:35PM -0400, Ashutosh Bapat wrote:
> The diffs are more than typos, they are grammatical changes and they are
> correct. So, the one who did those seems to be good at English grammar. Is
> it possible for him to help fix more of those errors. We can commit them
> all together in a single commit.

I know we already talked about this, but for the record and for people who just
read the list, let me explain again. Those errors were detected by lintian, the
Debian pacakge checker. As it turned out the solution for the third problem
even was wrong, more on that later.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

On Sat, May 19, 2012 at 06:10:21AM +0900, Michael Paquier wrote:
> Just, here is some feedback about the patch.
> The pages modified are man pages, so I suppose that the man pages in binary
> have been directly modified.
> It is more straightforward to modify directly sgml pages :)

Yeah, as I said I should have checked the patch before sending, sorry.

> Also, I found that the 3rd correction (create type) is not related to
> Postgres-XC documentation directly, the part corrected is exclusive to
> PostgreSQL, so it is more logic to correct that upstream on PostgreSQL.

And what makes it worse, the solution I send doesn't get it right either. The
whole sentence was kind of flawed. With the help of Stephen Frost at the
airport this morning I fixed this and committed said fix to postgresql git. So
with the next sync postgres-xc should be fine.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Just, here is some feedback about the patch.
The pages modified are man pages, so I suppose that the man pages in binary
have been directly modified.
It is more straightforward to modify directly sgml pages :)
Also, I found that the 3rd correction (create type) is not related to
Postgres-XC documentation directly, the part corrected is exclusive to
PostgreSQL, so it is more logic to correct that upstream on PostgreSQL.

I am committing however the 2 typo mistakes you found.
Thanks,

On Sat, May 19, 2012 at 6:04 AM, Ashutosh Bapat <
ash...@en...> wrote:

>
>
> On Fri, May 18, 2012 at 5:03 PM, Michael Paquier <
> mic...@gm...> wrote:
>
>> Yes it would be better of course, but this is a non-ending task,
>> and we might also get corrections from other people on different pages,
>> so we should correct those ones at least as long as we do not forget the
>> corrections we get.
>> I don't see any problems in correcting that with small commits, there are
>> a lot of such commits in postgres GIT repo :)
>
>
> Well, I suppose there are many such errors in our documentation I suppose
> :)
>
>
>>
>>
>> On Sat, May 19, 2012 at 5:53 AM, Ashutosh Bapat <
>> ash...@en...> wrote:
>>
>>> Hi Michael,
>>> I hope, I am not asking a lot, but here it is.
>>>
>>> The diffs are more than typos, they are grammatical changes and they are
>>> correct. So, the one who did those seems to be good at English grammar. Is
>>> it possible for him to help fix more of those errors. We can commit them
>>> all together in a single commit.
>>>
>>> On Fri, May 18, 2012 at 1:49 PM, Michael Meskes <me...@po...>wrote:
>>>
>>>> Hi,
>>>>
>>>> Debian package checker lintian found a couple typos in a couple
>>>> manpages.
>>>> Vladimir Stavrinov created a patch for it which I attach in hope of it
>>>> getting
>>>> applied to the upstream git.
>>>>
>>>> Michael
>>>> --
>>>> Michael Meskes
>>>> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
>>>> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
>>>> Jabber: michael.meskes at googlemail dot com
>>>> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Wishes,
>>> Ashutosh Bapat
>>> EntepriseDB Corporation
>>> The Enterprise Postgres Company
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>>
>>
>>
>> --
>> Michael Paquier
>> http://michael.otacoo.com
>>
>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Enterprise Postgres Company
>
>


-- 
Michael Paquier
http://michael.otacoo.com

On Fri, May 18, 2012 at 5:03 PM, Michael Paquier
<mic...@gm...>wrote:

> Yes it would be better of course, but this is a non-ending task,
> and we might also get corrections from other people on different pages, so
> we should correct those ones at least as long as we do not forget the
> corrections we get.
> I don't see any problems in correcting that with small commits, there are
> a lot of such commits in postgres GIT repo :)


Well, I suppose there are many such errors in our documentation I suppose :)


>
>
> On Sat, May 19, 2012 at 5:53 AM, Ashutosh Bapat <
> ash...@en...> wrote:
>
>> Hi Michael,
>> I hope, I am not asking a lot, but here it is.
>>
>> The diffs are more than typos, they are grammatical changes and they are
>> correct. So, the one who did those seems to be good at English grammar. Is
>> it possible for him to help fix more of those errors. We can commit them
>> all together in a single commit.
>>
>> On Fri, May 18, 2012 at 1:49 PM, Michael Meskes <me...@po...>wrote:
>>
>>> Hi,
>>>
>>> Debian package checker lintian found a couple typos in a couple manpages.
>>> Vladimir Stavrinov created a patch for it which I attach in hope of it
>>> getting
>>> applied to the upstream git.
>>>
>>> Michael
>>> --
>>> Michael Meskes
>>> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
>>> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
>>> Jabber: michael.meskes at googlemail dot com
>>> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>>
>>
>>
>> --
>> Best Wishes,
>> Ashutosh Bapat
>> EntepriseDB Corporation
>> The Enterprise Postgres Company
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>
>
> --
> Michael Paquier
> http://michael.otacoo.com
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Yes it would be better of course, but this is a non-ending task,
and we might also get corrections from other people on different pages, so
we should correct those ones at least as long as we do not forget the
corrections we get.
I don't see any problems in correcting that with small commits, there are a
lot of such commits in postgres GIT repo :)

On Sat, May 19, 2012 at 5:53 AM, Ashutosh Bapat <
ash...@en...> wrote:

> Hi Michael,
> I hope, I am not asking a lot, but here it is.
>
> The diffs are more than typos, they are grammatical changes and they are
> correct. So, the one who did those seems to be good at English grammar. Is
> it possible for him to help fix more of those errors. We can commit them
> all together in a single commit.
>
> On Fri, May 18, 2012 at 1:49 PM, Michael Meskes <me...@po...>wrote:
>
>> Hi,
>>
>> Debian package checker lintian found a couple typos in a couple manpages.
>> Vladimir Stavrinov created a patch for it which I attach in hope of it
>> getting
>> applied to the upstream git.
>>
>> Michael
>> --
>> Michael Meskes
>> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
>> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
>> Jabber: michael.meskes at googlemail dot com
>> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Enterprise Postgres Company
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Michael Paquier
http://michael.otacoo.com

Hi Michael,
I hope, I am not asking a lot, but here it is.

The diffs are more than typos, they are grammatical changes and they are
correct. So, the one who did those seems to be good at English grammar. Is
it possible for him to help fix more of those errors. We can commit them
all together in a single commit.

On Fri, May 18, 2012 at 1:49 PM, Michael Meskes <me...@po...>wrote:

> Hi,
>
> Debian package checker lintian found a couple typos in a couple manpages.
> Vladimir Stavrinov created a patch for it which I attach in hope of it
> getting
> applied to the upstream git.
>
> Michael
> --
> Michael Meskes
> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
> Jabber: michael.meskes at googlemail dot com
> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Thanks for those typo fixes.
Let me have a look at it and commit it.
BR,

On Fri, May 18, 2012 at 1:49 PM, Michael Meskes <me...@po...>wrote:

> Hi,
>
> Debian package checker lintian found a couple typos in a couple manpages.
> Vladimir Stavrinov created a patch for it which I attach in hope of it
> getting
> applied to the upstream git.
>
> Michael
> --
> Michael Meskes
> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
> Jabber: michael.meskes at googlemail dot com
> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
Michael Paquier
http://michael.otacoo.com

On Sat, May 19, 2012 at 03:44:35AM +0900, sat...@gm... wrote:
> The patch for ecpg documentation had been reviewed and committed
> by Peter Eisentraut.

Phew, I'm glad he covered my back.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Hi,

2012/5/19 Koichi Suzuki <koi...@gm...>:
> I believe some of them were committed.   Satoshi Nagayasu posted this.
>  I've just talked with you at the last year's PGCon.   I will check
> again but I believe it's okay.

Yes.
The patch for ecpg documentation had been reviewed and committed
by Peter Eisentraut.

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f7b15b5098ee89a2628129fbbef9901bded9d27b

I really appreciate him about that.

Regards,

>
> Regards;
> ----------
> Koichi Suzuki
>
>
> 2012/5/18 Michael Meskes <me...@po...>:
>> On Thu, May 17, 2012 at 03:05:09PM -0400, Koichi Suzuki wrote:
>>> We've met when NTT offered ECPG documentation.    I hope you remember
>>
>> Uh, oh, this kind of fell through the cracks. It hasn't been applied yet,
>> right? This is surely my fault. I simply forgot about it. Did you do any
>> changes on it recently? Or else should I work with the version you send me back
>> then?
>>
>> Please take my apologies for this.
>>
>> Michael
>> --
>> Michael Meskes
>> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
>> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
>> Jabber: michael.meskes at googlemail dot com
>> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers



-- 
--
NAGAYASU Satoshi <sat...@gm...>

I believe some of them were committed.   Satoshi Nagayasu posted this.
  I've just talked with you at the last year's PGCon.   I will check
again but I believe it's okay.

Regards;
----------
Koichi Suzuki


2012/5/18 Michael Meskes <me...@po...>:
> On Thu, May 17, 2012 at 03:05:09PM -0400, Koichi Suzuki wrote:
>> We've met when NTT offered ECPG documentation.    I hope you remember
>
> Uh, oh, this kind of fell through the cracks. It hasn't been applied yet,
> right? This is surely my fault. I simply forgot about it. Did you do any
> changes on it recently? Or else should I work with the version you send me back
> then?
>
> Please take my apologies for this.
>
> Michael
> --
> Michael Meskes
> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
> Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
> Jabber: michael.meskes at googlemail dot com
> VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL