On 16 September 2011 16:24, Susanne Ebrecht wrote:
> Isn't it possible to create a closed mailing list - a list that won't get
> published - on which
> I can discuss SQL Standard stuff with the folk who wants to support me?
>
> I don't fear to make decisions on my own - but speaking for the whole
Hello all,
what I saw on PHP unconference told me that I should ask all again.
I feel lonely. Believe me it is a bad feeling when it seems that nobody has
interests in what you are doing.
Since 4 years I am PostgreSQL representative in SQL Standard committee.
Always, when I suggested to talk a
On Thu, Sep 15, 2011 at 11:37 PM, Tom Lane wrote:
> This seems like it's already predetermining the outcome of the argument
> about recovery.conf. Mind you, I'm not unhappy with this choice, but
> it's hardly implementing only behavior that's not being debated.
>
> If we're satisfied with not tre
On Fri, Sep 16, 2011 at 7:53 AM, Simon Riggs wrote:
> This patch splits bgwriter into 2 processes: checkpointer and
> bgwriter, seeking to avoid contentious changes. Additional changes are
> expected in this release to build upon these changes for both new
> processes, though this patch stands on
On Thu, September 15, 2011 6:10 pm, Josh Kupershmidt wrote:
> On Thu, Sep 15, 2011 at 10:46 AM, Andrew Dunstan
> wrote:
>> this time with patch.
>
> I think help.c should document the \setenv command. And a link from
> the "Environment" section[1] of psql's doc page to the section about
> \setenv
Amit Kapila writes:
> I observed that during initialization of planstate for Append Node, we
> allocate ResulttupleSlot, however it is used only to send NULL slot indicate
> no more tuples.
> Is it right or there is any other purpose of it?
That also holds the plan's output tuple descriptor. I
On Thu, Sep 15, 2011 at 10:46 AM, Andrew Dunstan wrote:
> this time with patch.
I think help.c should document the \setenv command. And a link from
the "Environment" section[1] of psql's doc page to the section about
\setenv might help too.
The existing \set command lists all internal variables
On Thu, Sep 15, 2011 at 15:53, David E. Wheeler wrote:
> On Sep 15, 2011, at 4:41 PM, Alex Hunsaker wrote:
>
>> ExtUtils searches @INC, privlibexp maybe we should do that?
>
> Yes, I just got an email from David Golden to that effect. So perhaps the
> attached patch is better?
Close, seems I was
On Sep 15, 2011, at 4:41 PM, Alex Hunsaker wrote:
> ExtUtils searches @INC, privlibexp maybe we should do that?
Yes, I just got an email from David Golden to that effect. So perhaps the
attached patch is better?
Best,
David
xsubpp2.patch
Description: Binary data
--
Sent via pgsql-hackers
On Thu, Sep 15, 2011 at 10:44, David E. Wheeler wrote:
> Hackers,
>
> Since installing Perl 5.14.1, I installed newer version of ExtUtils::ParseXS
> from CPAN. I installed it with `make install UNINST=1`, which removes the
> copy of xsubpp that ships with core Perl. This results in an error duri
Jesper,
are you sure you have autovacuum configured properly, so posting lists don't
grow too much. It's true, that concurrency of posting lists isn't good, since
they all appended.
Oleg
On Thu, 15 Sep 2011, Jesper Krogh wrote:
Hi List.
This is just an "observation" I'll try to reproduce it i
On Thu, Sep 15, 2011 at 7:27 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> I've looked at the patch, and took a brief look at the paper - but I still
> don't understand the algorithm. I just can't get my head around the concepts
> of split pairs and left/right groups. Can
Hi List.
This is just an "observation" I'll try to reproduce it in a test set later.
I've been trying to performancetune a database system which does
a lot of updates on GIN indexes. I currently have 24 workers running
executing quite cpu-intensive stored procedures that helps generate
the body
Hackers,
Since installing Perl 5.14.1, I installed newer version of ExtUtils::ParseXS
from CPAN. I installed it with `make install UNINST=1`, which removes the copy
of xsubpp that ships with core Perl. This results in an error during PostgreSQL
`make`:
make -C plperl install
gcc -O2 -Wall -Wmi
Hi All,
I observed that during initialization of planstate for Append Node, we
allocate ResulttupleSlot, however it is used only to send NULL slot indicate
no more tuples.
Is it right or there is any other purpose of it?
Amit
***
On 14.09.2011 23:29, Robert Haas wrote:
On Mon, Aug 8, 2011 at 7:47 AM, Robert Haas wrote:
I've been thinking about this too and actually went so far as to do
some research and put together something that I hope covers most of
the interesting cases. The attached patch is pretty much entirely
u
On 2011-09-15 16:31, Cédric Villemain wrote:
There exist also a mecanism to order the parameters of 'EXECUTE ...
USING ...' (it's using a cursor), can the current work benefit to
EXECUTE USING to use named parameters ?
I looked at it a bit but it seems there is no benefit, since the dynamic
On 11.09.2011 22:30, Alexander Korotkov wrote:
Hackers,
I've got my patch with double sorting picksplit impementation for GiST into
more acceptable form. A little of testing is below. Index creation time is
slightly higher, but search is much faster. The testing datasets were
following:
1) unifo
On Thu, September 15, 2011 10:44 am, Andrew Dunstan wrote:
>
> As discussed, patch attached.
>
this time with patch.
setenv.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
As discussed, patch attached.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Fujii Masao writes:
> It seems to need a bit more time until we've reached a consensus about
> the treatment of recovery.conf. How about committing the core patch
> first, and addressing the recovery.conf issue as a different patch later?
> The attached patch provides a core part of the feature,
2011/9/15 Yeb Havinga :
> Hello list,
>
> The following patch implements cursor calling with named parameters in
> addition to the standard positional argument lists.
>
> c1 cursor (param1 int, param2 int) for select * from rc_test where a >
> param1 and b > param2;
> open c1($1, $2);
On Thu, Sep 15, 2011 at 5:58 AM, Peter Eisentraut wrote:
> Alternatively, we could just forget about the whole thing and move
> everything to postgresql.conf and treat recovery.conf as a simple empty
> signal file. I don't know if that's necessarily better.
Seems like it might be simpler.
--
R
On tor, 2011-09-15 at 16:54 +0900, Fujii Masao wrote:
> On Wed, Sep 14, 2011 at 6:33 PM, Peter Eisentraut wrote:
> > On tis, 2011-09-13 at 17:10 +0100, Simon Riggs wrote:
> >> So treat postgresql.conf as if it has an automatic "include
> >> recovery.conf" in it. The file format is the same.
> >
>
On Wed, Sep 14, 2011 at 6:21 PM, Kyotaro HORIGUCHI
wrote:
> Hi, This is a review for pg_last_xact_insert_timestamp patch.
> (https://commitfest.postgresql.org/action/patch_view?id=634)
Thanks for the review!
> Q1: The shmem entry for timestamp is not initialized on
> allocating. Is this OK? (I d
Fujii Masao writes:
> If we'd like to treat recovery.conf as if it's under the data directory, I'm
> afraid that we should add complicated code to parse recovery.conf after
> the value of data_directory has been determined from postgresql.conf.
> Furthermore, what if recovery.conf has another sett
Hello list,
The following patch implements cursor calling with named parameters in
addition to the standard positional argument lists.
c1 cursor (param1 int, param2 int) for select * from rc_test where a >
param1 and b > param2;
open c1($1, $2); -- this is currently possi
On Wed, Sep 14, 2011 at 6:33 PM, Peter Eisentraut wrote:
> On tis, 2011-09-13 at 17:10 +0100, Simon Riggs wrote:
>> So treat postgresql.conf as if it has an automatic "include
>> recovery.conf" in it. The file format is the same.
>
> Sounds good. That would also have the merit that you could use,
paulo matadr wrote:
[has problems displaying non-ASCII characters]
> Environment has been applied
> [postgres@gcomdesenv oracle]$ export
[...]
> declare -x NLS_LANG="AMERICAN_AMERICA.AL32UTF8"
The environment has not been applied correctly, because you
see question marks, which is Oracle's replac
On 2011-09-14 17:27, David E. Wheeler wrote:
On Sep 14, 2011, at 5:49 AM, Kaare Rasmussen wrote:
[brief]: http://postgresopen.org/2011/schedule/presentations/83/
You list Job scheduling as one item here,
but not here
Here's my preliminary list:
Could you expand your idea about this here?
I
30 matches
Mail list logo
