On Thu, Sep 4, 2014 at 12:42 PM, Stephen Frost sfr...@snowman.net wrote:
I'm certainly interested in the pgcrypto patches and can look at REINDEX
this weekend.
I'm thinking of picking one of these up, but I'll be on vacation next
week, and so probably won't get to it until the 15th at the
On Thu, Sep 4, 2014 at 03:48:17PM -0400, Robert Haas wrote:
On Thu, Sep 4, 2014 at 3:35 PM, Bruce Momjian br...@momjian.us wrote:
At any rate, I've additionally observed that the relation which is blowing
up
pg_upgrade is a VIEW in the source cluster but gets created as a TABLE in
the
2014-09-04 5:36 GMT+02:00 Peter Eisentraut pete...@gmx.net:
On Mon, 2014-05-19 at 13:51 -0400, Peter Eisentraut wrote:
On 5/18/14, 3:52 AM, Pavel Stehule wrote:
I am looking on --analyze-in-stages option. If I understand well,
motivation for this option is a get some minimal statistic
On Thu, Sep 4, 2014 at 11:56 AM, Bruce Momjian br...@momjian.us wrote:
I am thinking eventually we will need to cache the foreign server
statistics on the local server.
Wouldn't that lead to issues where the statistics get outdated and we have to
anyways query the foreign server
Stephen Frost wrote:
* Heikki Linnakangas (hlinnakan...@vmware.com) wrote:
5. Better syntax for REINDEX
I think the latter 3 patches are missing a reviewer because no-one
is interested in them. There was some discussion on the REINDEX
syntax, and whether we want the patch at all. The
On Thu, Sep 4, 2014 at 11:55 AM, Peter Geoghegan p...@heroku.com wrote:
It's not an immediate concern, though.
My immediate concern is to get some level of buy-in about how
everything fits together at a high level. Separately, as discussed in
my opening mail, there is the question of how value
On Thu, Sep 4, 2014 at 1:18 PM, David G Johnston
david.g.johns...@gmail.com wrote:
Specific observations would help though that is partly the idea - I've been
more focused on clarity and organization even if it requires deviating from
the current general documentation style.
OK.
- to the
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
Stephen Frost wrote:
* Heikki Linnakangas (hlinnakan...@vmware.com) wrote:
5. Better syntax for REINDEX
I think the latter 3 patches are missing a reviewer because no-one
is interested in them. There was some discussion on the
On Thu, Sep 4, 2014 at 2:12 PM, Peter Geoghegan p...@heroku.com wrote:
On Thu, Sep 4, 2014 at 9:19 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Sep 2, 2014 at 10:27 PM, Peter Geoghegan p...@heroku.com wrote:
* Still doesn't address the open question of whether or not we should
Doing the upgrade with an installation built from REL9_3_STABLE at
commit 52eed3d4267faf671dae0450d99982cb9ba1ac52 was successful.
The view that I saw get re-created as a table doesn't have any circular
references, or indeed any references to other views, nor do any other views
reference it. But
On Thu, Sep 4, 2014 at 2:31 PM, Josh Berkus j...@agliodbs.com wrote:
Sadly, what's prevented us from having packages already has been the
insistence of potential feature sponsors that they work *exactly* like
PL/SQL's packages, which is incompatible with Postgres namespacing.
Also, we'd want
On Thu, Sep 4, 2014 at 2:18 PM, Robert Haas robertmh...@gmail.com wrote:
Eh, maybe? I'm not sure why the case where we're using abbreviated
keys should be different than the case we're not. In either case this
is a straightforward trade-off: if we do a memcmp() before strcoll(),
we win if it
On Thu, Sep 4, 2014 at 03:24:05PM -0600, Noah Yetter wrote:
Doing the upgrade with an installation built from REL9_3_STABLE at
commit 52eed3d4267faf671dae0450d99982cb9ba1ac52 was successful.
The view that I saw get re-created as a table doesn't have any circular
references, or indeed any
On Thu, Sep 4, 2014 at 5:13 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Sep 4, 2014 at 1:18 PM, David G Johnston
david.g.johns...@gmail.com wrote:
Specific observations would help though that is partly the idea - I've
been
more focused on clarity and organization even if it
On Sep4, 2014, at 20:50 , Pavel Stehule pavel.steh...@gmail.com wrote:
2014-09-04 20:31 GMT+02:00 Josh Berkus j...@agliodbs.com:
* The ability to compile functions/procedures for faster execution.
This point is more complex, because bottleneck is not in plpgsql - it is
terrible fast against
Hi,
I noticed that a setting in pg_settings without units have NULL and
as unit values ( for integer and NULL for the other ones). Could we be
consistent? It is like that since units were introduced (b517e65). No
unit means unit = NULL. A proposed patch is attached.
--
Euler Taveira
On Thu, Sep 4, 2014 at 11:12 AM, Peter Geoghegan p...@heroku.com wrote:
What I
consider an open question is whether or not we should do that on the
first call when there is no abbreviated comparison, such as on the
second or subsequent attribute in a multi-column sort, in the hope
that
On Thu, Sep 4, 2014 at 5:07 PM, Peter Geoghegan p...@heroku.com wrote:
So I came up with what I imagined to be an unsympathetic case:
BTW, this cities data is still available from:
http://postgres-benchmarks.s3-website-us-east-1.amazonaws.com/data/cities.dump
--
Peter Geoghegan
--
Sent via
Hi all,
I am a graduate student from UC San Diego. My adviser, Dr. Kirill
Levchenko, and I have been working on a web/DB security project for
the last few months. Since fine-grained access control in DBMS is part
of our project and the PostgreSQL community is also working on it now,
we would like
Zhaomo,
* Zhaomo Yang (zhy...@cs.ucsd.edu) wrote:
I am a graduate student from UC San Diego. My adviser, Dr. Kirill
Levchenko, and I have been working on a web/DB security project for
the last few months. Since fine-grained access control in DBMS is part
of our project and the PostgreSQL
On 08/12/2014 10:58 AM, Robert Haas wrote:
What would really be ideal here is if the JSON code could inform the
toast compression code this many initial bytes are likely
incompressible, just pass them through without trying, and then start
compressing at byte N, where N is the byte following the
On 08/08/2014 10:21 AM, Andrew Dunstan wrote:
On 08/07/2014 11:17 PM, Tom Lane wrote:
I looked into the issue reported in bug #11109. The problem appears to be
that jsonb's on-disk format is designed in such a way that the leading
portion of any JSON array or object will be fairly
On 08/08/2014 11:18 AM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 08/07/2014 11:17 PM, Tom Lane wrote:
I looked into the issue reported in bug #11109. The problem appears to be
that jsonb's on-disk format is designed in such a way that the leading
portion of any JSON array
On Fri, Aug 22, 2014 at 1:35 PM, furu...@pm.nttdata.co.jp wrote:
Thank you for updating the patch.
I reviewed the patch.
First of all, I think that we should not append the above message to
section of '-r' option.
(Or these message might not be needed at all) Whether flush location in
On 04/09/14 14:42, Amit Kapila wrote:
On Thu, Sep 4, 2014 at 8:00 AM, Mark Kirkwood mark.kirkw...@catalyst.net.nz
wrote:
Hi Amit,
Results look pretty good. Does it help in the read-write case too?
Last time I ran the tpc-b test of pgbench (results of which are
posted earlier in this
2.1 The authentication problem
We address the authentication problem by requiring developers to
define an authentication function in the DBMS. This function is
invoked whenever an application-level user logs in. An authentication
function contains the authentication logic in the
Thanks for the review!
I understand the attention message wasn't appropriate.
To report the write location, even If you do not specify a replication
slot.
So the fix only appended messages.
There was a description of the flush location section of '-S' option,
but I intended to
Hello all!
I do some test with ODBC driver for PosgreSql, TimesTen MySQL. I compare
performance on very simple request. Database always located on same PC as
test application. Test PC - Lenovo T500, Cnetos 6.5 64, 8 Gb RAM, SSD.
I found what PostgreSql ODBC driver is slowest in comparison.
IMHO
101 - 128 of 128 matches
Mail list logo
