29.04.2011 21:18, Kevin Grittner wrote:
Vlad Arkhipov wrote:
But even if it would work it would not help me anyways. Because my
constraint is much more complex and depends on other tables, I
cannot express it in terms of exclusion constraints.
Are you aware of the changes to the SE
Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Wed, 2011-03-09 at 21:21 -0500, Bruce Momjian wrote:
> > > Simon Riggs wrote:
> > > > On Fri, 2011-03-04 at 23:15 +0900, Fujii Masao wrote:
> > > >
> > > > > postgres=# SELECT application_name, state, sync_priority, sync_state
> > > > > FROM pg_stat
On Thu, Feb 3, 2011 at 7:56 AM, Magnus Hagander wrote:
> Include more status information in walsender results
>
> Add the current xlog insert location to the response of
> IDENTIFY_SYSTEM
why was this third field added to SYSTEM_IDENTIFY? can't find any
place where it's used...
not even on BaseBa
On Apr 29, 2011, at 2:07 PM, Tom Lane wrote:
> In particular, src/include/nodes/plannodes.h is pretty well commented.
Ah, that's a useful file to scan, thanks.
> If it's not immediately obvious how that maps to what's shown by
> EXPLAIN, look into commands/explain.c.
Yeah, that's the file I hav
"Kevin Grittner" wrote:
> This'll take some study.
I've gone through the list of commands in the development docs with
an eye toward exposing anything else we might have missed in dealing
with the SSI predicate locking. Some of this needs further
research, but I'm posting what I have so far s
On Apr 29, 2011, at 5:19 PM, Joshua Berkus wrote:
> Beyond that, are we ready to set the schedule for 9.2 yet? I'd tend to say
> that:
>
> CF1: July 1-30
> CF2: Sept 1-21
> CF3: November 1-21
> CF4: January 3-31
Tom and I were talking about starting maybe June 1, rather than July 1. You
seem
"David E. Wheeler" writes:
> Is there any place where the contents of EXPLAIN nodes are documented?
Use the source, Luke ...
In particular, src/include/nodes/plannodes.h is pretty well commented.
If it's not immediately obvious how that maps to what's shown by
EXPLAIN, look into commands/explain
Thanks heikki.
@ashu: i am in final year undergrad at bangalore under vtu. I know the term
regression. Just did not know how to do that. Heikki reminded me skmething i
tried out while compiling binutils...make check. Will look into that.
Thanks for the help so far both of you. :)
On 29 Apr 2011 1
Excerpts from Dimitri Fontaine's message of vie abr 29 16:37:37 -0300 2011:
> Tom Lane writes:
> > It wasn't bothering me either initially, but the argument about the
> > command looking different when you suck it into an editor with \e
> > has some credibility.
>
> It still do not bother me the
Tom Lane writes:
> It wasn't bothering me either initially, but the argument about the
> command looking different when you suck it into an editor with \e
> has some credibility.
It still do not bother me the least, I much prefer PROMPT2 to be +>.
With emacs you use M-d then a rectangular cut (C
On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut wrote:
> On fre, 2011-04-22 at 08:37 -0500, Merlin Moncure wrote:
>> It wouldn't bother me in the lest that if in plpgsql procedures if you
>> had to set up and tear down a transaction on every line.
>
> It would probably be more reasonable and fea
Hackers,
Is there any place where the contents of EXPLAIN nodes are documented? I'm
making a lot of use of the XML format right now to figure out what queries sort
on what tables and with what columns, but I've had to do a lot of
experimentation to figure out what each type of node contains.
F
Tom Lane writes:
> Uh, no, the picksplit bugs we fixed were in cube and seg --- there's
> no reason to think that updating will help this. But 8.4's pgstattuple
> does appear to support gist indexes, so please run that and see what
> you get.
There's also gevel that I used to inspect in developm
On Fri, Apr 29, 2011 at 02:10:19PM -0400, Stephen Frost wrote:
> * Stephen Frost (sfr...@snowman.net) wrote:
> > Uhm.. With the above, perhaps "--%Z+>", which would generate:
> >
> > postgres=>
> > -- +>
>
> yah, obviously not going to work. :) However, it wouldn't be impossible
> to have
2011/4/29 Greg Stark :
> On Fri, Apr 29, 2011 at 5:45 PM, Christopher Browne
> wrote:
>> The "bike shedding" that I'd rather have would involve enclosing
>> prompts with /* comments */ so that cut'n'paste could be expected to
>> generate output that could run, without further editing, in another
Greg Stark writes:
> On Fri, Apr 29, 2011 at 5:45 PM, Christopher Browne
> wrote:
>> The "bike shedding" that I'd rather have would involve enclosing
>> prompts with /* comments */ so that cut'n'paste could be expected to
>> generate output that could run, without further editing, in another
>>
* Stephen Frost (sfr...@snowman.net) wrote:
> Uhm.. With the above, perhaps "--%Z+>", which would generate:
>
> postgres=>
> -- +>
yah, obviously not going to work. :) However, it wouldn't be impossible
to have psql recognize and strip "--+> " if/when it's seen
starting a new line, if we s
On Fri, Apr 29, 2011 at 5:45 PM, Christopher Browne wrote:
> The "bike shedding" that I'd rather have would involve enclosing
> prompts with /* comments */ so that cut'n'paste could be expected to
> generate output that could run, without further editing, in another
> psql session. Mind you, when
Christopher Browne writes:
>> Excerpts from David E. Wheeler's message of vie abr 29 13:04:35 -0300 2011:
>>> +1 I like this idea, so the prompt might by default be
>>>
>>> postgres=>
>>> +>
> That's certainly a reasonable sort of start.
> It seems like pretty serious bikesheddi
* Christopher Browne (cbbro...@gmail.com) wrote:
> It seems like pretty serious bikeshedding to try to come up with an
> operator to express "do as many of character X as the length of
> variable $FOO".
How about "pad with spaces to line up prompt", or such? In general, I
like the idea of having
"Mark Reid" writes:
> This morning I noticed that a normally small table (18 wide rows) was
> bloated to 6GB in size. This has happened before using older postgres
> versions in the past, where the main table got vacuumed, but the pg_toastXX
> table did not. This is the first time I've seen a pr
On Fri, Apr 29, 2011 at 12:17 PM, Alvaro Herrera
wrote:
> Excerpts from David E. Wheeler's message of vie abr 29 13:04:35 -0300 2011:
>> On Apr 29, 2011, at 8:22 AM, Tom Lane wrote:
>>
>> > AFAICT the initial prompt is always "mysql> ", so they don't have to
>> > think hard about how many spaces t
Excerpts from David E. Wheeler's message of vie abr 29 13:04:35 -0300 2011:
> On Apr 29, 2011, at 8:22 AM, Tom Lane wrote:
>
> > AFAICT the initial prompt is always "mysql> ", so they don't have to
> > think hard about how many spaces to insert to make it line up. But
> > we could certainly inven
On Apr 29, 2011, at 8:22 AM, Tom Lane wrote:
> AFAICT the initial prompt is always "mysql> ", so they don't have to
> think hard about how many spaces to insert to make it line up. But
> we could certainly invent a prompt escape that means "as many spaces
> as there are characters in the current
Magnus Hagander writes:
> On Fri, Apr 29, 2011 at 17:09, Tom Lane wrote:
>> ... Two different possible changes were suggested:
>>
>> * Drop the database name from PROMPT2, so you see
>>
>>postgres=>
>>->
> Definite -1 on that option - your query no longer lines up, and if you
>
All,
> +1 from me for keeping it as-is as well.
So it sounds like most committers want to keep the CFs on their existing
schedule for another year. Also that we don't want to branch until RC1. While
it would be nice to get some feedback from those who had bad experiences with
the CF cycle,
On Apr 26, 2011, at 6:08 PM, Kevin Grittner wrote:
> Josh Berkus wrote:
>> -- doing a backfill operation for 10GB of computed data, taking 8
>> hours, where I don't want to hold a transaction open for 8 hours
>> since this is a high-volume OLTP database.
>
> Been there, done that. Definitely not
On Fri, Apr 29, 2011 at 17:09, Tom Lane wrote:
> Over at
> http://archives.postgresql.org/pgsql-novice/2011-04/msg00102.php
> there's an interesting thread about a novice who forgot to put a
> semicolon at the end of his SQL commands, and what psql might do to be
> a little more friendly at the be
Over at
http://archives.postgresql.org/pgsql-novice/2011-04/msg00102.php
there's an interesting thread about a novice who forgot to put a
semicolon at the end of his SQL commands, and what psql might do to be
a little more friendly at the beginning of the learning curve. We see
similar complaints
On Apr 7, 2011, at 1:13 AM, Greg Smith wrote:
> On 04/05/2011 02:21 PM, Mischa Sandberg wrote:
>> Came across the following in a paper from Oct 2010. Was wondering is this is
>> old news I missed in this group.
>> http://pdos.csail.mit.edu/papers/linux:osdi10.pdf
>> about Linux optimization on mul
Vlad Arkhipov wrote:
> But even if it would work it would not help me anyways. Because my
> constraint is much more complex and depends on other tables, I
> cannot express it in terms of exclusion constraints.
Are you aware of the changes to the SERIALIZABLE transaction
isolation level in the
On 29.04.2011 13:19, Vaibhav Kaushal wrote:
I have a small db which I am using to test it. Moreover I am new to the
terms. What would you mean by 'regression'?
"make check"
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hacke
I have a small db which I am using to test it. Moreover I am new to the
terms. What would you mean by 'regression'?
Also, I am using eclipse for browsing the code. It resolves all references
and function calls, declarations, definitions etc.
Regards,
Vaibhav
On Fri, Apr 29, 2011 at 3:31 PM, Ashu
Is regression clean?
Have you looked at how the member is used using some code browsing tool like
cscope by examining it's every occurrence? PG uses simulated run time
polymorphism a lot, so any Node should examined carefully from that angle
too. Even after all of that if you think that it's not b
I tried all aggregates - min,max,sum,count and avg. all are working. What do
you suggest now?
On Fri, Apr 29, 2011 at 11:30 AM, Ashutosh Bapat <
ashutosh.ba...@enterprisedb.com> wrote:
>
>
> On Thu, Apr 28, 2011 at 4:21 PM, Vaibhav Kaushal <
> vaibhavkaushal...@gmail.com> wrote:
>
>> Thanks a lot
2011/4/28 Noah Misch
> In the mean time, have you considered doing something like this instead?
>
> EXCEPTION WHEN deadlock_detected
>RAISE NOTICE '% var_foo % var_bar', var_foo, var_bar;
>RAISE;
>
> The information isn't as nicely aggregated, but you don't lose any details.
>
Th
On Thu, Apr 28, 2011 at 02:49:07PM -0400, Andrew Dunstan wrote:
> I'll make that change if Michael's happy.
Sure, go ahead.
Thanks.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
On Thu, Apr 28, 2011 at 06:45:54PM +0200, Robert Haas wrote:
> Yeah, I think Dan's notes about memory ordering would be good to include.
I left it out initially because I didn't want to make things more
confusing. As far as memory ordering is concerned, this is the same
story as anything else that
38 matches
Mail list logo
