On Thu, Mar 8, 2012 at 8:40 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 29, 2012 at 9:39 PM, Fujii Masao masao.fu...@gmail.com wrote:
Do we have an updated patch? Fujii?
No. I believe that the author Jim will submit the updated version.
Jim, are you going to submit an updated
On Wed, Feb 29, 2012 at 9:39 PM, Fujii Masao masao.fu...@gmail.com wrote:
Do we have an updated patch? Fujii?
No. I believe that the author Jim will submit the updated version.
Jim, are you going to submit an updated version?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The
Excerpts from Heikki Linnakangas's message of jue ene 26 15:58:58 -0300 2012:
On 26.01.2012 17:31, Tom Lane wrote:
The idea that occurs to me is to have the code that uses the GUC do a
verify_mbstr(noerror) on it, and silently ignore it if it doesn't pass
(maybe with a LOG message). This
On Thu, Mar 1, 2012 at 4:13 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Heikki Linnakangas's message of jue ene 26 15:58:58 -0300 2012:
On 26.01.2012 17:31, Tom Lane wrote:
The idea that occurs to me is to have the code that uses the GUC do a
verify_mbstr(noerror) on
On 25.01.2012 15:29, Jim Mlodgenski wrote:
On Tue, Jan 24, 2012 at 7:38 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
There's one little problem remaining with this, which is what to do if the
message is in a different encoding than used by the client? That's not a new
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
The thing is, there's currently no encoding conversion happening, so if
you have one database in LATIN1 encoding and another in UTF-8, for
example, whatever you put in your postgresql.conf is going to be wrong
for one database.
On tor, 2012-01-26 at 10:34 +0200, Heikki Linnakangas wrote:
For postgresql.conf I think we could make a rule that it's always in
UTF-8. We haven't had to take a stance on the encoding used in
postgresql.conf before, but IMHO UTF-8 only would be quite reasonable.
We have so far violently
On 26.01.2012 17:31, Tom Lane wrote:
Heikki Linnakangasheikki.linnakan...@enterprisedb.com writes:
The thing is, there's currently no encoding conversion happening, so if
you have one database in LATIN1 encoding and another in UTF-8, for
example, whatever you put in your postgresql.conf is
On Tue, Jan 24, 2012 at 7:38 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 23.01.2012 22:52, Jim Mlodgenski wrote:
On Wed, Jan 18, 2012 at 9:19 AM, Jim Mlodgenskijimm...@gmail.com wrote:
On Wed, Jan 18, 2012 at 3:08 AM, Heikki Linnakangas
I don't think that's a
On Wed, Jan 18, 2012 at 9:19 AM, Jim Mlodgenski jimm...@gmail.com wrote:
On Wed, Jan 18, 2012 at 3:08 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 18.01.2012 07:49, Fujii Masao wrote:
On Fri, Jan 6, 2012 at 1:38 AM, Jim Mlodgenskijimm...@gmail.com wrote:
I have a
On 18.01.2012 07:49, Fujii Masao wrote:
On Fri, Jan 6, 2012 at 1:38 AM, Jim Mlodgenskijimm...@gmail.com wrote:
I have a need to send banner messages to a psql client that I can set
on the server and will be displayed on any psql client that connects
to the database. This would be mostly used
On Wed, Jan 18, 2012 at 3:08 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 18.01.2012 07:49, Fujii Masao wrote:
On Fri, Jan 6, 2012 at 1:38 AM, Jim Mlodgenskijimm...@gmail.com wrote:
I have a need to send banner messages to a psql client that I can set
on the server
On Fri, Jan 6, 2012 at 1:38 AM, Jim Mlodgenski jimm...@gmail.com wrote:
I have a need to send banner messages to a psql client that I can set
on the server and will be displayed on any psql client that connects
to the database. This would be mostly used as an additional indicator
to which
I have a need to send banner messages to a psql client that I can set
on the server and will be displayed on any psql client that connects
to the database. This would be mostly used as an additional indicator
to which database you are connecting, but could also be used by people
to force their
Jim Mlodgenski jimm...@gmail.com wrote:
Any feedback is welcome.
You might want to add it here to make sure it doesn't slip through the
cracks:
https://commitfest.postgresql.org/action/commitfest_view/open
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
15 matches
Mail list logo
