On Fri, Aug 16, 2013 at 11:12 PM, Alvaro Herrera
wrote:
> Robert Haas escribió:
>> On Fri, Aug 9, 2013 at 8:44 AM, Stephen Frost wrote:
>> > A shared catalog which defined which *database* to run the trigger in,
>> > with a way to fire off a new backend worker in that database and tell it
>> > to
On Fri, Aug 16, 2013 at 06:56:45PM -0500, Michael Cronenworth wrote:
> I started a thread on the general list so read that for more info.
>
> http://www.postgresql.org/message-id/520a6e55.40...@cchtml.com
>
> I'm also going to submit the patch to CommitFest.
> +#ifndef WIN32
> if (SO
On 08/16/2013 05:15 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Why not just call it pg_sleep_int()?
>
> To me, that looks like something that would take an int. I suppose you
> could call it pg_sleep_interval(), but that's getting pretty verbose.
>
> The larger picture here though is that tha
Josh Berkus writes:
> Why not just call it pg_sleep_int()?
To me, that looks like something that would take an int. I suppose you
could call it pg_sleep_interval(), but that's getting pretty verbose.
The larger picture here though is that that's ugly as sin; it just flies
in the face of the fac
On 08/16/2013 04:52 PM, Tom Lane wrote:
> Since the same effect can be had by writing a user-defined SQL function,
> I'm a bit inclined to say that the value-added by having this as a
> built-in function doesn't justify the risk of breaking existing apps.
> It's a close call though, because both th
I started a thread on the general list so read that for more info.
http://www.postgresql.org/message-id/520a6e55.40...@cchtml.com
I'm also going to submit the patch to CommitFest.
Thanks,
Michael
>From bb79da0013d5169b4530df28ece0c296004d1db4 Mon Sep 17 00:00:00 2001
From: Michael Cronenworth
Peter Eisentraut writes:
> On 8/16/13 3:35 PM, Robert Haas wrote:
>> On Fri, Aug 16, 2013 at 2:57 PM, Greg Stark wrote:
>>> Except there are no data types that can be cast to both double and
>>> interval currently.
>> That, unfortunately, is not sufficient to avoid a problem.
> That example can
On Thu, Aug 15, 2013 at 12:08:57PM -0500, Jon Nelson wrote:
> > Where are we on this issue?
>
> I've been able to replicate it pretty easily with PostgreSQL and
> continue to look into it. I've contacted Theodore Ts'o and have gotten
> some useful information, however I'm unable to replicate the b
On 8/15/13 2:58 PM, Jon Nelson wrote:
> Taking a look at PostgreSQL HEAD today, I noticed that pg_ctl
> documents that pg_ctl initdb takes OPTIONS but doesn't document them
> (unlike for start and others).
>
> Is this intentional?
The man page tells you that those are the options for regular init
On 8/16/13 3:35 PM, Robert Haas wrote:
> On Fri, Aug 16, 2013 at 2:57 PM, Greg Stark wrote:
>> Except there are no data types that can be cast to both double and
>> interval currently.
>
> That, unfortunately, is not sufficient to avoid a problem.
>
> rhaas=# create or replace function foo(doubl
On 16.8.2013 21:38, Robert Haas wrote:
> On Wed, Aug 14, 2013 at 12:13 AM, Jeff Janes
> wrote:
>> in 9.3 and 9.4, pgstat_reset_remove_files uses the global variable
>> pgstat_stat_directory rather than the argument it is passed,
>> "directory". On crash recovery, this means the tmp directory gets
On Wed, Aug 14, 2013 at 12:13 AM, Jeff Janes wrote:
> in 9.3 and 9.4, pgstat_reset_remove_files uses the global variable
> pgstat_stat_directory rather than the argument it is passed, "directory".
> On crash recovery, this means the tmp directory gets cleared twice and the
> permanent pg_stat does
On Fri, Aug 16, 2013 at 2:57 PM, Greg Stark wrote:
> Except there are no data types that can be cast to both double and
> interval currently.
That, unfortunately, is not sufficient to avoid a problem.
rhaas=# create or replace function foo(double precision) returns
double precision as $$select $
On Wed, Aug 14, 2013 at 8:04 AM, Michael Paquier
wrote:
> On Wed, Aug 14, 2013 at 10:10 AM, Robert Haas wrote:
>> I think Alvaro's suggestion is better. It's shorter, and makes clear
>> that at most one will be started.
> OK cool. Here are patches for 9.3 and master respecting those comments.
T
Except there are no data types that can be cast to both double and
interval currently.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Aug 13, 2013 at 4:11 PM, Greg Stark wrote:
> I'm not convinced using a ring buffer is necessarily that bad even if
> you want to vacuum as fast as possible. The reason we use a small ring
> buffer is to avoid poisoning the entire cache with vacuum pages, not
> to throttle the speed of vacu
On Thu, Aug 8, 2013 at 7:52 AM, Vik Fearing wrote:
> Someone on IRC a while ago was complaining that there was no way to
> specify an interval for pg_sleep, so I made one. Patch against today's
> HEAD attached.
>
> Usage: SELECT pg_sleep(interval '2 minutes');
The problem with this is that then
On Mon, Aug 12, 2013 at 1:26 AM, Michael Paquier
wrote:
> While playing a bit with background workers (commit 527ea66), I found that
> setting bgw_main for a dynamic bgworker, as well as bgw_library_name and
> bgw_library_name, crashes to server if the library defining the function
> defined in bg
Robert Haas escribió:
> On Fri, Aug 9, 2013 at 8:44 AM, Stephen Frost wrote:
> > A shared catalog which defined which *database* to run the trigger in,
> > with a way to fire off a new backend worker in that database and tell it
> > to run the trigger, might be interesting and would deal with the
On Fri, Aug 9, 2013 at 8:44 AM, Stephen Frost wrote:
> * Robert Haas (robertmh...@gmail.com) wrote:
>> On Sun, Aug 4, 2013 at 4:26 PM, Dimitri Fontaine
>> wrote:
>> > What I'm yet unsure about is that there's a consensus that the use cases
>> > are worthy of a new shared catalog in the system. A
On Mon, Aug 12, 2013 at 04:44:12PM -0400, Bruce Momjian wrote:
> On Mon, Aug 12, 2013 at 10:08:07PM +0200, Pavel Raiskup wrote:
> > > The patch moves the atexit setting up, as you suggested, but only does
> > > that when pg_ctl succeeds (we know we started the server),
> >
> > Yes, of course!
> >
maybe your C++ program has something (such as charset or configuation) causing
this strange thing
mark
发件人： "ciifrance...@tiscali.it"
收件人： ha...@2ndquadrant.com
抄送： pgsql-hackers@postgresql.org; pgsql-zh-gene...@postgresql.org;
pgsql-ru-gene...@postgresql.
On Tue, Jul 23, 2013 at 11:53 AM, Albe Laurenz wrote:
> Magnus Hagander wrote:
>> In that case, doesn't this patch break Windows? We no longer do the
>> anonymous bind on Windows, since it's now in the #ifdef HAVE_LIBLDAP.
>>
>> Don't we need to keep the ldap_simple_bind() call in the Windows case
[I reply to both in one email]
Song:
that C++ program has a log file.
In the log file the queries look like this:
UPDATE MY_table SET
UTF8_field =
'<8f><20><31><32><33><34><27><20><57><48><45><52><45><20><49><44><20><3d><20><31>
starting from the first chinese letter, all the rest of the quer
Thanks for your answer.
Yes, the client is also UTF8:
MyDB=# show
client_encoding;
client_encoding
-
UTF8
(1 row)
Cheers
Francesco
Messaggio originale
Da: ha...@2ndquadrant.com
Data: 16/08/2013 14.16
A: "ciifrance...@tiscali.it"
Cc: , ,
Ogg: Re:
[HACKERS] Chinese i
On 08/16/2013 02:40 PM, ciifrance...@tiscali.it wrote:
> Thanks for your answer.
> Yes, the client is also UTF8:
>
> MyDB=# show
> client_encoding;
> client_encoding
> -
> UTF8
> (1 row)
Strange, it works for me :
hannu@hannu-900X3E:~/workspace/my-app$ psql
psql (9.3beta2, serve
On 08/16/2013 01:25 PM, ciifrance...@tiscali.it wrote:
> Hello all,
> before writing this message, I wrote about this in other mailing lists
> without solving my problem.
> Maybe some of you can help me.
>
> I have problems with a DB in postgres, when i try to insert Chinese
> strings in UTF-8 form
Hello all,
before writing this message, I wrote about this in other mailing lists without
solving my problem.
Maybe some of you can help me.
I have problems with a DB in postgres, when i try to insert Chinese strings in
UTF-8 format.
If I insert the data using a C++ program I have empty squares,
28 matches
Mail list logo
