2009/10/27 Simon Riggs si...@2ndquadrant.com:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional point that would be useful is a way to match up the usage
of custom_variable_classes with this new style of .conf file processing.
At the moment if you wish to add a
I would like to add a temporal contrib module. The most important piece
would be adding a period data type and some support functions. Jeff
Davis and I both have temporal projects on pgFoundry, and we've been
collaborating for a while. But there are some areas we'd like to get
some advice on.
On Wed, 2009-10-28 at 12:51 -0700, Jeff Davis wrote:
Trying to develop and document a set of standardized, stable hash
functions covering a wide range of possible use cases sounds like it may
be better served by an extension.
I suspect that some of the participants in this thread have PL/Proxy
2009/10/29 Scott Bailey arta...@comcast.net:
I would like to add a temporal contrib module. The most important piece
would be adding a period data type and some support functions. Jeff Davis
and I both have temporal projects on pgFoundry, and we've been collaborating
for a while. But there are
Hello
I got a possibility to continue on GROUPING SETS see
http://wiki.postgresql.org/wiki/Grouping_Sets
My last patch was based on an sharing functionality with non recursive
CTE. I would to recapitulate all options here and I would to prepare
this patch for next commitfest.
a) using
On Thu, 2009-10-29 at 09:47 +0200, Peter Eisentraut wrote:
On Wed, 2009-10-28 at 12:51 -0700, Jeff Davis wrote:
Trying to develop and document a set of standardized, stable hash
functions covering a wide range of possible use cases sounds like it may
be better served by an extension.
I
Scott Bailey wrote:
I would like to add a temporal contrib module. The most important piece
would be adding a period data type and some support functions. Jeff
Davis and I both have temporal projects on pgFoundry, and we've been
collaborating for a while.
I presume you're going to need some
On Friday 30 November at 1200 GMT, the server that hosts our primary
FTP server, GIT server and one of the website mirrors will be moved to
a new data center. Downtime is expected to be two to three hours.
Apologies for any inconvenience this may cause.
--
Dave Page
EnterpriseDB UK:
Heikki Linnakangas wrote:
Scott Bailey wrote:
I would like to add a temporal contrib module.
I'm very pleased to see people working on temporal issues, BTW!
Me too - common use-case and difficult to handle without the right
types/operators.
Nulls - A common use case for periods is for
Hi,
So, I'll take over the work if there are no ones to do it.
I'm thinking to add syntax support first. Table partitioning was
proposed many times, but it is still not applied into core.
The reason is it is too difficult to make perfect partitioning
feature at once. I think syntax support
On Tue, 2009-10-27 at 20:40 -0700, Josh Berkus wrote:
If you require that a tool (or SET PERISTENT) parse through a file in
order to change one setting, then you've just doubled or tripled the
code size of the tool, as well as added a host of failure conditions
which wouldn't have existed
On Wed, 2009-10-28 at 09:39 -0700, Greg Stark wrote:
On Wed, Oct 28, 2009 at 7:33 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Greg Smith escribió:
This sounds familiar...oh, that's right, this is almost the same
algorithm pgtune uses. And it sucks,
It's also a blatant
Le dimanche 25 octobre 2009 10:08:33, Peter Eisentraut a écrit :
On lör, 2009-10-24 at 13:32 -0400, Greg Smith wrote:
Regardless, the UI I was hoping for was to make the default
postgresql.conf file end with a line like this:
directory 'conf'
I think something like is this is
Pavel Stehule wrote:
2009/10/27 Simon Riggs si...@2ndquadrant.com:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional point that would be useful is a way to match up the usage
of custom_variable_classes with this new style of .conf file
2009/10/29 Andrew Dunstan and...@dunslane.net:
Pavel Stehule wrote:
2009/10/27 Simon Riggs si...@2ndquadrant.com:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional point that would be useful is a way to match up the usage
of custom_variable_classes with
2009/10/29 Andrew Dunstan and...@dunslane.net:
Pavel Stehule wrote:
2009/10/27 Simon Riggs si...@2ndquadrant.com:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional point that would be useful is a way to match up the usage
of custom_variable_classes with
Pavel Stehule wrote:
2009/10/29 Andrew Dunstan and...@dunslane.net:
Pavel Stehule wrote:
2009/10/27 Simon Riggs si...@2ndquadrant.com:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional point that would be useful is a way
On Wed, 2009-10-28 at 15:11 +0100, Anders Steinlein wrote:
Is there any interest in expanding \dn+ to show schema size, similar
to table sizes using \dt+ in 8.4? We use separate schemas for each
user, so this would allow us to quickly look up the sizes of each
user's data.
A schema
Hannu Krosing ha...@2ndquadrant.com writes:
Or maybe we could just extract the hashes form some version of stock
postgresql (say 8.3) and then make those available in contrib under the
name stable_hashes ?
A better name would be wishful_thinking ... contrib does not have
control over some of
On Thu, Oct 29, 2009 at 11:19 AM, Peter Eisentraut pete...@gmx.net wrote:
On Wed, 2009-10-28 at 15:11 +0100, Anders Steinlein wrote:
Is there any interest in expanding \dn+ to show schema size, similar
to table sizes using \dt+ in 8.4? We use separate schemas for each
user, so this would
Andrew Dunstan and...@dunslane.net writes:
Anyway, it seems to me a whole lot better than inventing a new thing
that makes custom_variable_class as something to append to
custom_variable_classes. If you're going to insist on using append
foo = 'x' at least let it apply to the list that is
On 29 Oct 2009, at 02:15, Itagaki Takahiro wrote:
I'd like to improve partitioning feature in 8.5.
Kedar-san's previous work is wonderful, but I cannot see any updated
patch.
http://archives.postgresql.org/message-id/bd8134a40906080702s96c90a9q3bbb581b9bd0d...@mail.gmail.com
So, I'll take
On Thu, 2009-10-29 at 09:32 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
Or maybe we could just extract the hashes form some version of stock
postgresql (say 8.3) and then make those available in contrib under the
name stable_hashes ?
A better name would be
Robert Haas robertmh...@gmail.com writes:
To be honest, I'm not entirely comfortable with either behavior.
Pipelining a delete out of one table into an insert into another table
seems VERY useful to me, and I'd like us to have a way to do that. On
the other hand, in more complex cases, the
Thom Brown thombr...@gmail.com writes:
custom_variable_classes = 'x'
custom_variable_classes += 'y'
custom_variable_classes = 'z'
That would result in the first 2 assignments being undone.
That's why I don't see how having as many files as you want to *for tool
based* configuration is a
Really, they don't know any Perl or Python or Java either? Maybe.
Anyway, it seems to me a whole lot better than inventing a new thing that
makes custom_variable_class as something to append to
custom_variable_classes. If you're going to insist on using append foo =
'x' at least let it
On Thu, 2009-10-29 at 12:31 +, Thom Brown wrote:
2009/10/29 Andrew Dunstan and...@dunslane.net:
Why not allow something like += or .= instead of the = to denote appending
to a list?
custom_variable_classes += 'x'
seems a whole lot nicer to me.
I would see that as making
On Thu, Oct 29, 2009 at 9:44 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Dunstan and...@dunslane.net writes:
Anyway, it seems to me a whole lot better than inventing a new thing
that makes custom_variable_class as something to append to
custom_variable_classes. If you're going to insist on
Joshua D. Drake wrote:
On Thu, 2009-10-29 at 12:31 +, Thom Brown wrote:
2009/10/29 Andrew Dunstan and...@dunslane.net:
Why not allow something like += or .= instead of the = to denote appending
to a list?
custom_variable_classes += 'x'
seems a whole lot nicer to me.
Robert Haas robertmh...@gmail.com writes:
Another option would be to introduce a section syntax, something like
what M$ does. We could define a line that contains just [foo] to mean
define foo as a custom variable class and automatically put all the
rest of the settings in this section into
Andrew Dunstan and...@dunslane.net writes:
The whole config file is a joke. We'd never do it the way we do if we
were designing it from scratch,
Why not, pray tell? We did design it from scratch, once upon a time,
and I don't see that the design is so obviously broken that we'd not
do the
* Peter Eisentraut (pete...@gmx.net) wrote:
On Wed, 2009-10-28 at 15:11 +0100, Anders Steinlein wrote:
Is there any interest in expanding \dn+ to show schema size, similar
to table sizes using \dt+ in 8.4? We use separate schemas for each
user, so this would allow us to quickly look up
On Thu, 2009-10-29 at 11:42 -0400, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
The whole config file is a joke. We'd never do it the way we do if we
were designing it from scratch,
Why not, pray tell? We did design it from scratch, once upon a time,
and I don't see that
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
The whole config file is a joke. We'd never do it the way we do if we
were designing it from scratch,
Why not, pray tell? We did design it from scratch, once upon a time,
and I don't see that the design is so obviously
Hello to all,
I'm a young programmer student, and I would like to realize TPR-index on
Postgresql system. Of course I want to use GiST template, rather than
writing core :)
I have some questions, and I would be very grateful if anybody answers my
question.
1) where could I know the prototypes of
On Thu, Oct 29, 2009 at 11:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Another option would be to introduce a section syntax, something like
what M$ does. We could define a line that contains just [foo] to mean
define foo as a custom variable class and
Itagaki Takahiro wrote:
The keyword PARTITION is
added to the full-reserved keyword list to support ADD/DROP PARTITION.
Any chance to avoid that? PARTITION seems like something people might
well use as a column or variable name. OTOH, it is reserved in SQL2008
and SQL2003.
--
Heikki
On Thu, 2009-10-29 at 09:32 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
Or maybe we could just extract the hashes form some version of stock
postgresql (say 8.3) and then make those available in contrib under the
name stable_hashes ?
A better name would be
Joshua D. Drake j...@commandprompt.com writes:
In regards to parsing files in a directory. It makes sense. Why the
implementation is so difficult is beyond me. Can't we just look at
Apache and say, Gee, it may not be perfect but it does everything we
need, let's use their implementation.?
Hi,
Sergej Galkin sergej.gal...@gmail.com writes:
1) where could I know the prototypes of such functions as union,
pentaly and etc. And to read more detally than in PostgreSql
documentation ?
Have you read that yet?
http://www.postgresql.org/docs/8.4/interactive/gist-implementation.html
On Thu, Oct 29, 2009 at 3:35 AM, Nikhil Sontakke
nikhil.sonta...@enterprisedb.com wrote:
So +1 on solidifying the syntax first and then sorting out the other
minute, intricate details later..
I like that idea as well but I have a concern. What will we do with
pg_dump. If the PARTITION commands
On Thursday 29 October 2009 18:33:22 Greg Stark wrote:
On Thu, Oct 29, 2009 at 3:35 AM, Nikhil Sontakke
nikhil.sonta...@enterprisedb.com wrote:
So +1 on solidifying the syntax first and then sorting out the other
minute, intricate details later..
I like that idea as well but I have a
On Thu, 2009-10-29 at 00:31 -0700, Scott Bailey wrote:
Nulls - A common use case for periods is for modeling valid time. Often
the end point is not known. For instance, you know when an employee has
been hired but the termination time typically wouldn't be known ahead of
time. We can
On Thu, 2009-10-29 at 09:37 +, Richard Huxton wrote:
There are cases where one time is genuinely unknown, and there we need
a null.
The semantics of a period with one side NULL require a more clear
definition. I don't personally see a lot of utility in trying to support
NULL semantics, but
I would like to add a temporal contrib module. The most important piece
would be adding a period data type and some support functions. Jeff
Davis and I both have temporal projects on pgFoundry, and we've been
collaborating for a while.
I presume you're going to need some backend support and
On Thu, 2009-10-29 at 10:54 +0200, Heikki Linnakangas wrote:
I presume you're going to need some backend support and possibly new
syntax for some of the operations, right? That seems more urgent to
discuss than the possible inclusion into contrib.
There are various areas that need work inside
All of this *also* applies to shared_preload_libraries. We also need to
be able to specify new load libraries without editing the same darn
parameter.
---
On Wed, 2009-10-28 at 22:00 +, Simon Riggs wrote:
On Tue, 2009-10-27 at 00:38 -0400, Greg Smith wrote:
new feature
One additional
Dear,
I have few suggestions about new features of postgresql.
1.Replication and clustering
included in core of postgresql
2.other
support beter olap and data warehouse solutions.
support bulk load with c-api.
thanks
marko
On Thu, Oct 29, 2009 at 3:46 PM, Marko marko_iva...@yahoo.com wrote:
Dear,
I have few suggestions about new features of postgresql.
1.Replication and clustering
included in core of postgresql
There are projects being worked on in this area, and add-on products
like Slony that can be used
On tor, 2009-10-29 at 11:15 +0900, Itagaki Takahiro wrote:
Range partitioning:
CREATE TABLE table_name ( columns )
PARTITION BY RANGE ( a_expr )
(
PARTITION name VALUES LESS THAN [(] const [)],
PARTITION name VALUES LESS THAN [(] MAXVALUE [)] -- overflow partition
On Fri, 2009-10-30 at 00:10 +0200, Peter Eisentraut wrote:
On tor, 2009-10-29 at 11:15 +0900, Itagaki Takahiro wrote:
Range partitioning:
CREATE TABLE table_name ( columns )
PARTITION BY RANGE ( a_expr )
(
PARTITION name VALUES LESS THAN [(] const [)],
PARTITION
On tis, 2009-09-01 at 14:29 -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
I think we should always or never show the view definition, not sometimes.
Yeah. I can live with \d not showing it and \d+ showing it --- as Peter
already mentioned, that would be consistent with
There is a gap in the permission scheme for inheritance setups. Say you
have this:
CREATE TABLE persons (...);
CREATE TABLE employees (...) INHERITS (persons);
GRANT SELECT ON persons TO foo;
Then user foo can extract who the employees are using
SELECT * FROM persons EXCEPT SELECT * FROM ONLY
On Thu, Oct 29, 2009 at 7:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Pipelined execution would be nice but I really doubt that it's worth
what we'd have to give up to have it. The one-at-a-time behavior will
be simple to understand and reliable to use. Concurrent execution won't
be either.
I
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
The keyword PARTITION is
added to the full-reserved keyword list to support ADD/DROP PARTITION.
Any chance to avoid that? PARTITION seems like something people might
well use as a column or variable name. OTOH, it is reserved
On Thu, Oct 29, 2009 at 9:51 PM, Itagaki Takahiro
itagaki.takah...@oss.ntt.co.jp wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
The keyword PARTITION is
added to the full-reserved keyword list to support ADD/DROP PARTITION.
Any chance to avoid that? PARTITION seems
Peter Eisentraut pete...@gmx.net wrote:
On tor, 2009-10-29 at 11:15 +0900, Itagaki Takahiro wrote:
Range partitioning:
CREATE TABLE table_name ( columns )
PARTITION BY RANGE ( a_expr )
(
PARTITION name VALUES LESS THAN [(] const [)],
PARTITION name VALUES LESS
On Thu, Oct 29, 2009 at 7:14 PM, Robert Haas robertmh...@gmail.com wrote:
CREATE TABLE does not require PARTITION to be a reserved keyword,
but there are conflicts in ALTER TABLE ADD/DROP PARTITION:
* ALTER TABLE ... DROP [COLUMN] name [CASCADE | RESTRICT]
* ALTER TABLE ... DROP PARTITION
Peter Eisentraut pete...@gmx.net writes:
There is a gap in the permission scheme for inheritance setups. Say you
have this:
CREATE TABLE persons (...);
CREATE TABLE employees (...) INHERITS (persons);
GRANT SELECT ON persons TO foo;
Then user foo can extract who the employees are using
Greg Stark gsst...@mit.edu wrote:
* ALTER TABLE ... DROP [COLUMN] name [CASCADE | RESTRICT]
* ALTER TABLE ... DROP PARTITION name [CASCADE | RESTRICT]
Do we need a DROP PARTITION command at all? What would it even do?
Currently no. So, it would be good to treat PARTITION as
just a
60 matches
Mail list logo
