On Tue, Apr 6, 2010 at 07:29, Takahiro Itagaki
wrote:
>
> Tom Lane wrote:
>
>> > - cygwin_conv_to_full_win32_path(cmdLine, buf);
>> > + cygwin_conv_path(CCP_POSIX_TO_WIN_A, cmdLine, buf, sizeof(buf));
>>
>> Buildfarm member brown_bat didn't like this. Seeing that that's the
>> *only* active
To follow up on the discussion here:
http://archives.postgresql.org/pgsql-docs/2010-02/msg00039.php
It seems like a big oversight that there's no way to insert quotes in
strings in recovery.conf. In the long run, the parsing should be done
the same way as postgresql.conf, or the two files be merg
Dne 6.4.2010 7:57, Joseph Adams napsal(a):
On Tue, Apr 6, 2010 at 1:00 AM, Petr Jelinek wrote:
Not really sure about this myself, but keep in mind that NULL has special
meaning in SQL.
To me, the most logical approach is to do the obvious thing: make
JSON's 'null' be SQL's NULL. For
Hackers,
Followup to Josh's posts.
I'm getting Bricolage 2.0 ready to ship, and took some time to test it on
PostgreSQL 9.0 today. I built PostgreSQL from Git/master with:
./configure --with-libs=/usr/local/lib
--with-includes=/usr/local/include --prefix=$BASE --with-perl PERL=$PERL
T
On Tue, Apr 6, 2010 at 3:29 AM, Simon Riggs wrote:
> I was also surprised to note that the Startup process is not signaled by
> WALReceiver when new WAL is received, so it will continue sleeping even
> though it has work to do.
I don't think this is so useful in 9.0 since synchronous replication
Hackers,
Continuing the performance test:
DBD, like a number of monitoring systems, does "pings" on the database
which look like this:
SELECT 'DBD::Pg ping test';
In our test, which does 5801 of these pings during the test, they take
an average of 15x longer to execute on 9.0 as 8.4 ( 0.77ms vs
All,
Wheeler has been doing some head-to-head performance testing of
Bricolage performance on 8.4 vs. 9.0. So far, 9.0 has been slower, and
I've been trying to track down the particular areas where it is.
One appears to be prepared query parsing. One test of the Bricolage
test suite creates 89
Tom Lane wrote:
> > - cygwin_conv_to_full_win32_path(cmdLine, buf);
> > + cygwin_conv_path(CCP_POSIX_TO_WIN_A, cmdLine, buf, sizeof(buf));
>
> Buildfarm member brown_bat didn't like this. Seeing that that's the
> *only* active cygwin buildfarm member, that's not a good percentage.
Hmmm, b
Dne 6.4.2010 5:50, Joseph Adams napsal(a):
Another JSON strictness issue: the JSON standard (
http://www.ietf.org/rfc/rfc4627.txt ) states that JSON text can only
be an array or object. However, my implementation currently accepts
any valid value. Thus, '3', '"hello"', 'true', 'false', and 'nu
On Mon, Apr 5, 2010 at 11:50 PM, Joseph Adams
wrote:
> In my opinion, we should accept an atomic value as valid JSON content.
That seems right to me.
> Also, should we go even further and accept key:value pairs by themselves? :
>
> '"key":"value"'::JSON
Definitely not.
...Robert
--
Sent via
Another JSON strictness issue: the JSON standard (
http://www.ietf.org/rfc/rfc4627.txt ) states that JSON text can only
be an array or object. However, my implementation currently accepts
any valid value. Thus, '3', '"hello"', 'true', 'false', and 'null'
are all accepted by my implementation, bu
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> Bruce Momjian writes:
> >>> + Exclusion constraints ensure that if any two rows are compared on
> >>> + the specified columns or expressions using the specified operators,
> >>> + at least one of these operator compariso
Hitoshi Harada wrote:
> Just note, I rebooted the guest VM today and retried but things are as
> before. The host reboot doesn't affect either.
Bad luck. :-(
> I also tried another CentOS5.4 VM on the same VirtualBox and succeeded
> to build. Another RHEL Server 5.2 (Tikanga) x86_64 real machi
On Mon, Apr 5, 2010 at 4:18 PM, Simon Riggs wrote:
> On Mon, 2010-04-05 at 15:58 -0400, Tom Lane wrote:
>> Simon Riggs writes:
>> > (errmsg("recovery command file \"%s\"
>> > specified neither primary_conninfo nor restore_command",
>> > -
On Mon, 2010-04-05 at 15:58 -0400, Tom Lane wrote:
> Simon Riggs writes:
> > (errmsg("recovery command file \"%s\"
> > specified neither primary_conninfo nor restore_command",
> > -
> > RECOVERY_COMMAND_FILE)))
Greg,
> http://wiki.postgresql.org/wiki/Regression_Testing_with_pgbench for this
> purpose, and it looks like you started where I ended that, more or less,
> which is good because you didn't duplicate anything I'd already
> written.
Lucky! I didn't find that one when I looked.
FWIW, the new pgb
Josh Berkus wrote:
I started with pgbench performance comparisons:
http://wiki.postgresql.org/wiki/Pgbenchtesting
I'd already created
http://wiki.postgresql.org/wiki/Regression_Testing_with_pgbench for this
purpose, and it looks like you started where I ended that, more or less,
which is
Simon Riggs writes:
> (errmsg("recovery command file \"%s\"
> specified neither primary_conninfo nor restore_command",
> -
> RECOVERY_COMMAND_FILE)));
> +
On Mon, Apr 5, 2010 at 3:42 PM, Simon Riggs wrote:
> On Mon, 2010-04-05 at 15:02 -0400, Alvaro Herrera wrote:
>> Simon Riggs escribió:
>> > On Mon, 2010-04-05 at 17:08 +0900, Fujii Masao wrote:
>> > > On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs
>> > > wrote:
>> > > > Log Message:
>> > > > --
On Mon, 2010-04-05 at 15:02 -0400, Alvaro Herrera wrote:
> Simon Riggs escribió:
> > On Mon, 2010-04-05 at 17:08 +0900, Fujii Masao wrote:
> > > On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs wrote:
> > > > Log Message:
> > > > ---
> > > > Check compulsory parameters in recovery.conf in stand
Simon Riggs escribió:
> On Mon, 2010-04-05 at 17:08 +0900, Fujii Masao wrote:
> > On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs wrote:
> > > Log Message:
> > > ---
> > > Check compulsory parameters in recovery.conf in standby_mode, per docs.
> >
> > On the recent discussion (*1), some peopl
On Mon, 2010-04-05 at 19:29 +0100, Simon Riggs wrote:
> Looking through the code some more I note that their are two timing
> related parameters that are hardcoded into XLogPageRead(). At the very
> least such things should be #defines, though one of them was previously
> configurable using pg_sta
On Mon, 2010-04-05 at 17:08 +0900, Fujii Masao wrote:
> On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs wrote:
> > Log Message:
> > ---
> > Check compulsory parameters in recovery.conf in standby_mode, per docs.
>
> On the recent discussion (*1), some people argued that specifying neither
> p
On Mon, 2010-04-05 at 18:03 +0900, Fujii Masao wrote:
> I'm leaning toward postponing the item to v9.1 or later.
If you want to defer anything, then I'd like to get a summary of what
you are thinking of deferring and why that is acceptable. Right now
there are lots of unfinished items and no move
On Mon, 2010-04-05 at 19:01 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > I am very disconcerted that there are still no docs whatsoever to
> > describe how the server works in these new modes.
>
> I did add a few paragraphs last week, see
> http://developer.postgresql.org/pgdocs/postg
2010/4/5 Kevin Grittner :
> Robert Haas wrote:
>
>> You can do:
>>
>> SELECT COUNT(*) FROM (SELECT DISTINCT profile.id, profile.name,
>> profile.age FROM ...) x;
>
> Ah, I see what they wanted now. In older versions of PostgreSQL,
> they might get better performance in some cases by using GROUP B
Patch attached to show the schema *and* table name when doing
a REINDEX DATABASE.
--
Greg Sabino Mullane g...@endpoint.com g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8
Index: backend/commands/indexcmds.c
===
RCS file:
Robert Haas wrote:
> You can do:
>
> SELECT COUNT(*) FROM (SELECT DISTINCT profile.id, profile.name,
> profile.age FROM ...) x;
Ah, I see what they wanted now. In older versions of PostgreSQL,
they might get better performance in some cases by using GROUP BY:
SELECT COUNT(*) FROM
(SELECT
On Sun, Apr 4, 2010 at 10:26 AM, Loïc Vaumerel wrote:
[...]
> All solutions I found are working the same way : they use dblink.
> I consider these solution more as handiwork than a clean solution.
> I am a little bit concerned about side effects as dblink were not intially
> designed for this.
>
Simon Riggs wrote:
> I am very disconcerted that there are still no docs whatsoever to
> describe how the server works in these new modes.
I did add a few paragraphs last week, see
http://developer.postgresql.org/pgdocs/postgres/warm-standby.html#STANDBY-SERVER-OPERATION.
It doesn't explicitly tal
On Sat, Apr 3, 2010 at 8:59 AM, junaidmalik14 wrote:
>
> Is there any alternative of mysql function COUNT(DISTINCT expr,[expr...]) in
> postgres. We get error if we
>
> write count like this count(distinct profile.id, profile.name, profile.age)
> but it works well in mysql.
>
> Reference url is gi
2010/4/5 Giles Lean :
>
> Josh Berkus wrote:
>
>> Could this be an issue with VirtualBox? Have you used this VM for
>> testing before?
>
> I'm not sure that this helps much as it doesn't rule out
> VirtualBox, but my experience with it running Linux has
> been positive. I do reboot the host at t
On Sun, Apr 4, 2010 at 10:26 AM, Loïc Vaumerel wrote:
> Is there a way to use real and clean autonomous transactions in PostgreSQL
> yet ?
No.
> If no, is it planned to do so ? When ?
To my knowledge, no one is working on this.
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
junaidmalik14 wrote:
> Is there any alternative of mysql function COUNT(DISTINCT
> expr,[expr...]) in postgres. We get error if we write count like
> this count(distinct profile.id, profile.name, profile.age)
Is that semantically different from this SQL standard syntax?:
SELECT profile.id, p
Bruce Momjian writes:
> Tom Lane wrote:
>> Bruce Momjian writes:
>>> + Exclusion constraints ensure that if any two rows are compared on
>>> + the specified columns or expressions using the specified operators,
>>> + at least one of these operator comparisons will be false. The syntax
Hi,
I have an application project based on a database.
I am really interested in using PostgreSQL.
I have only one issue, I want to use autonomous transactions to put in place
a debug / logging functionality.
To do so, I insert messages in a "debug" table.
The problem is, if the main transaction
Is there any alternative of mysql function COUNT(DISTINCT expr,[expr...]) in
postgres. We get error if we
write count like this count(distinct profile.id, profile.name, profile.age)
but it works well in mysql.
Reference url is given below
http://dev.mysql.com/doc/refman/5.1/en/group-by-functi
On Apr 2, 2010, at 6:07 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> b) The tag isn't actually version-stamped. configure/configure.in
>> still
>> say 9.0devel.
>
> Sure, because the tag is on a branch. According to the commit message
> that went by, Robert did that correctly:
>
> http://
Peter Eisentraut writes:
> b) The tag isn't actually version-stamped. configure/configure.in still
> say 9.0devel.
Sure, because the tag is on a branch. According to the commit message
that went by, Robert did that correctly:
http://archives.postgresql.org/pgsql-committers/2010-03/msg00378.php
On fre, 2010-04-02 at 14:44 -0400, Robert Haas wrote:
> On Apr 2, 2010, at 12:34 PM, Kevin Grittner
> wrote:
> > Josh Berkus wrote:
> >
> >> Robert,
> >
> >> do you think you could put up replacement tarballs today?
> >
> > If you don't hear from him soon, perhaps he's traveling:
> >
> > http://a
Takahiro Itagaki writes:
> Do we still need VACUUM FULL in initdb? VACUUM FULL in 9.0 rewrites
> all tables, so those operations are a little more expensive than
> previous releases. Is it worth replacing them into VACUUM?
I had left it that way intentionally to make sure there was nothing
depend
Takahiro Itagaki writes:
> Any objections for the following fix?
> - cygwin_conv_to_full_win32_path(cmdLine, buf);
> + cygwin_conv_path(CCP_POSIX_TO_WIN_A, cmdLine, buf, sizeof(buf));
Buildfarm member brown_bat didn't like this. Seeing that that's the
*only* active cygwin buildfarm membe
Magnus, Thanks your help.
When I set 64bit version of zlib1.dll, msvcr80.dll and msvcr90.dll into
Windows\system32 directory correctiry, it run well.
(Perhaps I did copy with MSYS's "cp command that does not work on
system directory.)
On Mon, 5 Apr 2010 11:44:53 +0200
Magnus Hagander wrote:
Hi Sergej,
you can found many scientific conferences having an application (or
demonstration) session. I am sure that your work will interest them.
Some scientific conferences having a demonstration session:
- Very Large Data Base (VLDB);
- International Conference on Data Engineering (ICDE);
Hello to all,
I realized index for moving objects in PostgreSQL DB, using GisT and I want
to write an article in the conference. It will be not a scientific paper,
but application track.
Can anybody tell the conference where I could publish my work ? :)
Best regards,
Sergej Galkin
On Mon, Apr 5, 2010 at 7:34 AM, Simon Riggs wrote:
> On Mon, 2010-04-05 at 07:11 -0400, Robert Haas wrote:
>> On Mon, Apr 5, 2010 at 4:46 AM, Simon Riggs wrote:
>> > On Wed, 2010-03-31 at 23:54 +0300, Heikki Linnakangas wrote:
>> >> Robert Haas wrote:
>> >> > Agreed. I think if the server starts
On Mon, 2010-04-05 at 07:11 -0400, Robert Haas wrote:
> On Mon, Apr 5, 2010 at 4:46 AM, Simon Riggs wrote:
> > On Wed, 2010-03-31 at 23:54 +0300, Heikki Linnakangas wrote:
> >> Robert Haas wrote:
> >> > Agreed. I think if the server starts up in standby mode and it is an
> >> > inconsistent state
On Sun, 2010-04-04 at 12:19 -0400, Tom Lane wrote:
> Hitoshi Harada writes:
> > I cannot figure out at all what is wrong. Have any idea?
>
> Since nobody else is reporting this, it seems like it must be either
> something messed up about your system, or something wrong with your
> copy of the PG
On Mon, Apr 5, 2010 at 4:46 AM, Simon Riggs wrote:
> On Wed, 2010-03-31 at 23:54 +0300, Heikki Linnakangas wrote:
>> Robert Haas wrote:
>> > Agreed. I think if the server starts up in standby mode and it is an
>> > inconsistent state with no source of WAL, then the startup process
>> > should exi
On Mon, Apr 5, 2010 at 07:16, TAKATSUKA Haruka wrote:
> Hi, all.
>
> I built pgsql with following regulation (for buildfarm new entry).
> - Windows Server 2008 64bit
> - VC2005
> - 9.0dev (HEAD near alpha5) 64bit
>
> And I got a fail at "vcregress contribcheck" about only pgcrypto.
> All CREATE
On Mon, 2010-04-05 at 17:08 +0900, Fujii Masao wrote:
> On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs wrote:
> > Log Message:
> > ---
> > Check compulsory parameters in recovery.conf in standby_mode, per docs.
>
> On the recent discussion (*1), some people argued that specifying neither
> p
On Mon, Feb 15, 2010 at 3:45 PM, Fujii Masao wrote:
> On Fri, Feb 12, 2010 at 11:46 PM, Tom Lane wrote:
>> Even more to the point is that some of them, like PGPORT, are highly
>> likely to be set in a server's environment to point to the server
>> itself. It would be extremely dangerous to autom
On Wed, 2010-03-31 at 23:54 +0300, Heikki Linnakangas wrote:
> Robert Haas wrote:
> > Agreed. I think if the server starts up in standby mode and it is an
> > inconsistent state with no source of WAL, then the startup process
> > should exit with a suitable error message, which AIUI will result in
On Sat, Apr 3, 2010 at 6:50 AM, Simon Riggs wrote:
> Log Message:
> ---
> Check compulsory parameters in recovery.conf in standby_mode, per docs.
On the recent discussion (*1), some people argued that specifying neither
primary_conninfo nor restore_command in the standby mode is not unrea
On Sat, Apr 3, 2010 at 12:26 AM, Tom Lane wrote:
> I disapprove of the whole approach, actually. The right way to fix this
> is to not touch or replace libpq at all, but to change walreceiver to
> use libpq's async-query facilities directly. Instead of PQexec, use
> PQsendQuery and then a loop i
55 matches
Mail list logo
