On Friday, October 26, 2012 10:59 AM Amit Kapila wrote:
> On Thursday, October 25, 2012 9:46 PM Jan Wieck wrote:
> > On 10/25/2012 10:12 AM, Stephen Frost wrote:
> > > Jan,
> > >
> > > * Jan Wieck (janwi...@yahoo.com) wrote:
> > >> The problem case this patch is dealing with is rolling window
> tab
On Friday, October 26, 2012 11:50 AM Jan Wieck wrote:
> On 10/26/2012 1:29 AM, Amit Kapila wrote:
> > On Thursday, October 25, 2012 9:46 PM Jan Wieck wrote:
> >> On 10/25/2012 10:12 AM, Stephen Frost wrote:
> >> > Jan,
> >> >
> >> > * Jan Wieck (janwi...@yahoo.com) wrote:
> >> >> The problem case t
On Thursday, October 25, 2012 11:04 PM Amit kapila wrote:
> On Thursday, October 25, 2012 5:43 AM, Noah Misch wrote:
> On Tue, Oct 23, 2012 at 08:21:54PM -0400, Noah Misch wrote:
> >> -Patch- -tps@-c1- -tps@-c2- -tps@-c8- -WAL@-c8-
> >> HEAD,-F80 816 1644
On 10/25/12 1:53 PM, David E. Wheeler wrote:
> I'm thinking of Pod as the precedent here, but I think most of the popular
> programming language ecosystems offer something like this (JavaDoc, rdoc,
> etc.).
The advantage that these programming language ecosystems have is that
they can implement
On 10/26/2012 6:35 AM, Amit Kapila wrote:
On Friday, October 26, 2012 11:50 AM Jan Wieck wrote:
On 10/26/2012 1:29 AM, Amit Kapila wrote:
>One other way could be to check after every few pages for a
conflicting
> lock request.
How is this any different from what my patch does?
The diffe
Hi,
This patch adds an empty row before each section header
in the error codes table in the docs.
I tried not putting an empty row before the first
section, but it looks better to always have
an empty row. IMO.
File: errorcode_table.patch
Applies against head.
Regards,
Karl
Free Software:
Hi,
The attached patch, raise_using_keyword_table.patch,
puts the pl/pgsql RAISE USING keywords into a table,
replacing a prose description.
Against HEAD.
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
diff --git a/doc/src/sgml/plpgsql.sgml b
On 10/26/2012 09:58:05 AM, Karl O. Pinc wrote:
> The attached patch, raise_using_keyword_table.patch,
> puts the pl/pgsql RAISE USING keywords into a table,
> replacing a prose description.
I'm attaching a v2 of this patch:
raise_using_keyword_table-v2.patch
The use of the word "keyword" does no
On Oct 26, 2012, at 5:27 AM, Peter Eisentraut wrote:
>
> The advantage that these programming language ecosystems have is that
> they can implement the processors for the documentation format in the
> language itself, so it's easy to recommend or enforce a particular
> system. I don't think we'
Rushabh Lathia writes:
> *-- Hitting all the partition table*
> postgres=# explain select a , ( select city_id from measurement where *logdate
> = test.b and logdate = '2006-02-02')* xyz from test;
Hm. What's happening here is that you get an equivalence class
containing logdate, test.b, and '20
On Fri, Oct 26, 2012 at 10:39 PM, Tom Lane wrote:
> Rushabh Lathia writes:
> > *-- Hitting all the partition table*
> > postgres=# explain select a , ( select city_id from measurement where
> *logdate
> > = test.b and logdate = '2006-02-02')* xyz from test;
>
> Hm. What's happening here is that
Alvaro Herrera wrote:
> Kevin Grittner escribió:
>> Tom Lane wrote:
>
>>> Also, it doesn't appear that we ever got around to preparing
>>> documentation updates, but I think we definitely need some if
>>> we're going to start throwing errors for things that used to be
>>> allowed. Since Kevin has
> Well, per our discussion here in person, I'm not convinced that this
> buys us anything in the "let's replace AMQ" case. However, as I pointed
> out in my last email, this feature doesn't need to replace AMQ to be
> useful. Let's focus on the original use case of supplying a queue which
> Lond
On 10/26/2012 10:23:56 AM, Karl O. Pinc wrote:
> On 10/26/2012 09:58:05 AM, Karl O. Pinc wrote:
>
> > The attached patch, raise_using_keyword_table.patch,
> > puts the pl/pgsql RAISE USING keywords into a table,
> > replacing a prose description.
Attached is: raise_using_keyword_table-v3.patch
It
On Thursday, October 18, 2012 09:58:20 PM Alvaro Herrera wrote:
> Here is version 22 of this patch. This version contains fixes to issues
> reported by Andres, as well as a rebase to latest master.
Ok, I now that pgconf.eu has ended I am starting to do a real review:
* Is it ok to make FOR UPDAT
On Thu, Oct 25, 2012 at 05:34:14PM +, Amit kapila wrote:
> I have fixed all the review comments raised in delta encoding approach raised
> by you (for needs toast, for now I have kept the code as it will not go in
> patch of encoding for it. however it can be changed.).
> I have also fixed th
On Thu, Oct 25, 2012 at 4:25 AM, Simon Riggs wrote:
> I'd put these in a separate directory to avoid annoyance. Transam is
> already too large.
+1. A further advantage of that is that it means that that everything
in that new directory will be intended to end up as
all-separately-compilable, whi
I just had this thought a few minutes ago, discussed it briefly with
RhodiumToad on #postgresql and wanted to put it out here for discussion.
Feel free to rip it apart. It probably is a bit "al-dente" at this point
and needs more cooking.
The reason why we need full_page_writes is that we need
I just had this thought a few minutes ago, discussed it briefly with
RhodiumToad on #postgresql and wanted to put it out here for discussion.
Feel free to rip it apart. It probably is a bit "al-dente" at this point
and needs more cooking.
The reason why we need full_page_writes is that we need
19 matches
Mail list logo
