In addition to the few patches left in Needs Review state, we have six
patches marked as Ready for Committer.
Committers: Could you please pick a patch, and commit if appropriate? Or
if there's a patch there that you think should *not* be committed,
please speak up.
- Heikki
--
Sent via pg
On Mon, Oct 6, 2014 at 1:15 PM, Tom Lane wrote:
> Michael Paquier writes:
> > Nothing really fancy:
> > $ ./configure --enable-depend --enable-debug --disable-rpath
> > --enable-cassert --prefix=/to/path/bin/pgsql --with-libxml
>
> That looks about like mine too, though I'm not using --disable-r
Michael Paquier writes:
> On Mon, Oct 6, 2014 at 12:21 PM, Tom Lane wrote:
>> [ scratches head... ] Doesn't reproduce on my OSX Mavericks laptop,
>> either with or without --disable-integer-datetimes.
>> What compiler are you using exactly?
> clang from developer tools 6.0 of September 2014, ev
On Mon, Oct 6, 2014 at 12:21 PM, Tom Lane wrote:
> Michael Paquier writes:
> > This morning while running make check-world on my OSX Mavericks laptop, I
> > found the following failure:
>
> [ scratches head... ] Doesn't reproduce on my OSX Mavericks laptop,
> either with or without --disable-in
Michael Paquier writes:
> This morning while running make check-world on my OSX Mavericks laptop, I
> found the following failure:
[ scratches head... ] Doesn't reproduce on my OSX Mavericks laptop,
either with or without --disable-integer-datetimes. What compiler
are you using exactly? Any sp
Hi,
This morning while running make check-world on my OSX Mavericks laptop, I
found the following failure:
test pgtypeslib/dt_test2 ... stderr FAILED (test process was
terminated by signal 6: Abort trap)
(lldb) bt
* thread #1: tid = 0x, 0x7fff8052c866
libsystem_kernel.dylib`__pthread_
Craig Ringer writes:
> While looking at an unrelated issue in PgJDBC I noticed that it's
> difficult for users and the driver to tell in advance if a given
> statement will support bind parameters.
It's not that hard ;-) ... if it ain't SELECT/INSERT/UPDATE/DELETE,
it won't accept parameters.
>
On Mon, Oct 6, 2014 at 4:17 AM, Fabrízio de Royes Mello
wrote:
> On Sun, Oct 5, 2014 at 9:52 AM, Marti Raudsepp wrote:
>> CREATE INDEX ... [ IF NOT EXISTS name | name ] ON ...
>>
>> Maybe I'm just slow, but it took me a few minutes to understand what
>> this means. :)
>
> Well, I try to show that
On Fri, Oct 3, 2014 at 9:51 PM, Heikki Linnakangas
wrote:
> So I now have a refactoring patch ready that I'd like to commit (the
attached two patches together), but to be honest, I have no idea why the
second patch is so essential to performance.
Thanks. I did some more tests with master, master+p
Hi all
While looking at an unrelated issue in PgJDBC I noticed that it's
difficult for users and the driver to tell in advance if a given
statement will support bind parameters.
PostgreSQL just treats placeholders as syntax errors for non-plannable
statements at parse time.
This forces users to
On Sun, Oct 5, 2014 at 9:52 AM, Marti Raudsepp wrote:
>
> > The version 5 (attached) contains all discussed until now.
>
> From documentation:
>
> CREATE INDEX ... [ IF NOT EXISTS name | name ] ON ...
>
> Maybe I'm just slow, but it took me a few minutes to understand what
> this means. :)
>
Well
Gavin Flower writes:
> The use of an /as_at_date/ is far more problematic. The idea relates to
> how existing date/times should be treated with respect to the date/time
> that a pg database is updated with new time zone data files. In the
> simplest form: there would be a function in pg that
On 06/10/14 10:33, Tom Lane wrote:
I got interested in the problem discussed in
http://www.postgresql.org/message-id/20714.1412456...@sss.pgh.pa.us
to wit:
It's becoming clear to me that our existing design whereby zone
abbreviations represent fixed GMT offsets isn't really good enough.
I've be
On 2014-10-03 18:29:23 +0300, Heikki Linnakangas wrote:
> On 10/03/2014 05:26 PM, Andres Freund wrote:
> >On 2014-10-03 17:12:18 +0300, Heikki Linnakangas wrote:
> >>On 09/28/2014 01:54 AM, Andres Freund wrote:
> >>>0003 Sinval/notify processing got simplified further. There really isn't
> >>>
I got interested in the problem discussed in
http://www.postgresql.org/message-id/20714.1412456...@sss.pgh.pa.us
to wit:
> It's becoming clear to me that our existing design whereby zone
> abbreviations represent fixed GMT offsets isn't really good enough.
> I've been wondering whether we could ch
Pavel,
* Pavel Stehule (pavel.steh...@gmail.com) wrote:
> Please, can you show me some use case, where OR has bigger sense than AND?
[...]
> > You might also have a policy which applies to all roles and then a more
> > permissive policy for an 'admin' type of user- look at the "Unix passwd"
> > ex
2014-10-05 14:16 GMT+02:00 Stephen Frost :
> * Pavel Stehule (pavel.steh...@gmail.com) wrote:
> > I am playing with RLS. I created simple table
> >
> > table_data (inserted_by text, v integer);
> >
> > I created two policies
> >
> > create policy p1 on data with check (inserted_by = session_user);
On Fri, Oct 3, 2014 at 7:25 PM, Fabrízio de Royes Mello
wrote:
> I agree with your grammar change.
Cool.
> The version 5 (attached) contains all discussed until now.
From documentation:
CREATE INDEX ... [ IF NOT EXISTS name | name ] ON ...
Maybe I'm just slow, but it took me a few minutes to
* Pavel Stehule (pavel.steh...@gmail.com) wrote:
> I am playing with RLS. I created simple table
>
> table_data (inserted_by text, v integer);
>
> I created two policies
>
> create policy p1 on data with check (inserted_by = session_user);
> create policy p2 on data with check (v between 10 and
Also, Платон Малюгин, can you add this patch to postgresql commitfest (
http://commitfest.postgresql.org)?
--
Ali Akbar
2014-10-05 15:21 GMT+07:00 Ali Akbar :
> Hi
> Oops, it seems that I have been too hasty here. With a fresh mind I looked
> at my own patch again and found two bugs:
>
>
>>> - Incorrect calculation of each step's value, making stuff crash, it is
>>> necessary to switch to the context of the functio
Hello
I am playing with RLS. I created simple table
table_data (inserted_by text, v integer);
I created two policies
create policy p1 on data with check (inserted_by = session_user);
create policy p2 on data with check (v between 10 and 1000);
I was surprised so p2 effectively disables p1;
ne
Hi
Oops, it seems that I have been too hasty here. With a fresh mind I looked
at my own patch again and found two bugs:
>
>> - Incorrect calculation of each step's value, making stuff crash, it is
>> necessary to switch to the context of the function to perform operations on
>> a temporary variabl
On 8/13/14, 5:14 AM, MauMau wrote:
I'm interested in b, too. I was thinking of proposing a performance
diagnostics feature like Oracle's wait events (V$SYSTEM_EVENT and
V$SESSION_EVENT). So, if you do this, I'd like to contribute to the
functional design, code and doc review, and testing.
I
Hello Heikki,
Here are new patches, again the first one is just refactoring, and the second
one contains this feature. I'm planning to commit the first one shortly, and
the second one later after people have had a chance to look at it.
I looked at it. It looks ok, but for a few spurious spac
25 matches
Mail list logo
