High Availability, Load Balancing, and Replication Feature Matrix
In the table no bull mark is in "No conflict resolution necessary" row for pgpool-II. Actually this is wrong. Pgpool-II does not need conflict resolution. Also in the same page "Pgpool-II has this capability." (here "this" means "Multiple-Server Parallel Query Execution") This used to be true long time ago but current stable versions of Pgpool-II do not support this any more. Attached patch fixes these. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
Re: High Availability, Load Balancing, and Replication Feature Matrix
Oops. Forgot to attach the patch. > In the table no bull mark is in "No conflict resolution necessary" row > for pgpool-II. Actually this is wrong. Pgpool-II does not need > conflict resolution. > > Also in the same page "Pgpool-II has this capability." (here "this" > means "Multiple-Server Parallel Query Execution") This used to be true > long time ago but current stable versions of Pgpool-II do not support > this any more. > > Attached patch fixes these. > > Best regards, > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese:http://www.sraoss.co.jp > > diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 89f6d6eda6..a824d383f2 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -429,7 +429,7 @@ protocol to make nodes agree on a serializable transactional order. • • - + • • @@ -471,8 +471,7 @@ protocol to make nodes agree on a serializable transactional order. concurrently on a single query. It is usually accomplished by splitting the data among servers and having each server execute its part of the query and return results to a central server where they - are combined and returned to the user. Pgpool-II - has this capability. Also, this can be implemented using the + are combined and returned to the user. This can be implemented using the PL/Proxy tool set.
Re: Client parameter list omits timezone
Greetings, * PG Doc comments form (nore...@postgresql.org) wrote: > Page: https://www.postgresql.org/docs/11/libpq-connect.html > Description: > > I am looking for a complete list of parameters that I can pass in the > "connect"/"open database connection" list on the client (in this case, > github.com/lib/pq). > > The list of parameters documented here: > https://www.postgresql.org/docs/11/libpq-connect.html#LIBPQ-PARAMKEYWORDS > does not include the "timezone" parameter. However, github.com/lib/pq seems > to indicate that "timezone" is an acceptable parameter, for example, here: > https://github.com/lib/pq/blob/master/encode_test.go#L123 The documentation you're looking at on postgresql.org is for the libpq C driver (which is written and maintained as part of core PostgreSQL), not for the Go driver that's at github.com/lib/pq. For my part, it doesn't seem like a good idea for the Go driver to deviate in this way, but you'd have to talk to the author of it about that, not us. Then again, that git repo also says at the bottom that it's not actively being developed and recommends a different Go driver be used. > Elsewhere in the docs, the PGTZ environment variable can be used to set the > timezone on the client. This is true, for the libpq driver. I don't know about the Go driver. > I would expect to see "timezone" (and anything else that can be configured) > in that list. 'timezone' isn't accepted by libpq, which is what our documentation is referring to. Thanks, Stephen signature.asc Description: PGP signature
Potential Error
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/tutorial-fk.html Description: Hello Thank you for your great tutorial. I wasn't able to compile the below without a 'not null' after the primary key word: https://www.postgresql.org/docs/current/tutorial-fk.html Just flagging in case it needs to be updated. Thanks, Ashok
Please ignore my last message
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/tutorial-fk.html Description: It was my mistake, please ignore it. Sorry I don't know how to recall
Re: Client parameter list omits timezone
I guess my broader issue is that it's hard to figure out how to configure things like the timezone in a given client. Generally, you pass some things as parameters in the connection string but it's not obvious which values are accepted or where to pass them, unless you go rooting around in the protocol details and the source code of the client, which is more than most users will or should be asked to do. Kevin On Sun, Jul 26, 2020 at 8:00 AM Stephen Frost wrote: > Greetings, > > * PG Doc comments form (nore...@postgresql.org) wrote: > > Page: https://www.postgresql.org/docs/11/libpq-connect.html > > Description: > > > > I am looking for a complete list of parameters that I can pass in the > > "connect"/"open database connection" list on the client (in this case, > > github.com/lib/pq). > > > > The list of parameters documented here: > > > https://www.postgresql.org/docs/11/libpq-connect.html#LIBPQ-PARAMKEYWORDS > > does not include the "timezone" parameter. However, github.com/lib/pq > seems > > to indicate that "timezone" is an acceptable parameter, for example, > here: > > https://github.com/lib/pq/blob/master/encode_test.go#L123 > > The documentation you're looking at on postgresql.org is for the libpq > C driver (which is written and maintained as part of core PostgreSQL), > not for the Go driver that's at github.com/lib/pq. > > For my part, it doesn't seem like a good idea for the Go driver to > deviate in this way, but you'd have to talk to the author of it about > that, not us. Then again, that git repo also says at the bottom that > it's not actively being developed and recommends a different Go driver > be used. > > > Elsewhere in the docs, the PGTZ environment variable can be used to set > the > > timezone on the client. > > This is true, for the libpq driver. I don't know about the Go driver. > > > I would expect to see "timezone" (and anything else that can be > configured) > > in that list. > > 'timezone' isn't accepted by libpq, which is what our documentation is > referring to. > > Thanks, > > Stephen >
Re: Client parameter list omits timezone
Greetings, Please don't top-post on these lists. * Kevin Burke (ke...@meter.com) wrote: > I guess my broader issue is that it's hard to figure out how to configure > things like the timezone in a given client. Generally, you pass some things > as parameters in the connection string but it's not obvious which values > are accepted or where to pass them, unless you go rooting around in the > protocol details and the source code of the client, which is more than most > users will or should be asked to do. As I said in my previous reply, you need to discuss that with the maintainer of that driver. The documentation you found does, accurately, reflect what options can be passed for the driver that it is the documentation for- namely the libpq C driver. Thanks, Stephen signature.asc Description: PGP signature
