On Fri, Oct 30, 2009 at 08:44:52PM +0900, Hitoshi Harada wrote:
> So, by chance, I have been working on plv8 for my own purpose and
> query like below is done:
>
> regression=# CREATE OR REPLACE FUNCTION plv8_test(keys text[], vals
> text[]) RETURNS text AS $$
> var o = {};
> for(var i=0; i o[ke
On Fri, Oct 30, 2009 at 11:02 AM, John Murtari wrote:
>
> The project web site has a lot of info, but here is a quick
> example of what it does:
>
> thebook=# show statistics * from db history;
> db | minutes | Questions | Connections | Com_delete
> -++
Jeff Janes writes:
> So my conclusions are:
> 2) Heavy-weight locks are called that for a reason, they use a lot of
> CPU even without contention.
> 3) The CPU usage of the hash-index code proper is quite small, with
> more time being spent in heavy-weight PageLocks (specific to hash
> indexes,
On Fri, 30 Oct 2009, John Murtari wrote:
We now have a basic patch set that works and is basically stable (not
recommended for production servers!). We've dedicated a page at our web
site and it hopefully has answers to most of your questions, and also
has the patch set for download. These a
On Sun, Oct 4, 2009 at 7:13 PM, Tom Lane wrote:
> Jeff Janes writes:
>> I see that the docs were recently changed from discouraging hash
>> indexes both because they were no known uses in which they were
>> meaningfully better than btree, and because they aren't recoverable;
>> to now just discou
Hi,
One of our customers is running 8.2.14 and use a couple of pl/perl and
pl/perlu functions written by CMD. Everything worked normally until
they tried to call one particular pl/perl function from pl/perl via
spi. It appears that a die call inside the callee just crashes the
backend. He
Robert Haas writes:
> IMO, the real problem is that the type interface is poorly
> encapsulated. There's way too much code that knows about the internal
> details of a type - namely, that it's a 32-bit integer modified by a
> second 32-bit integer. I think there are still places where the code
>
On Fri, 2009-10-30 at 17:39 -0400, Robert Haas wrote:
> IMO, the real problem is that the type interface is poorly
> encapsulated. There's way too much code that knows about the internal
> details of a type - namely, that it's a 32-bit integer modified by a
> second 32-bit integer. I think there
On Fri, Oct 30, 2009 at 5:16 PM, Tom Lane wrote:
> Jeff Davis writes:
>> I haven't looked at all of these places yet, so maybe a few simple
>> changes would allow us to treat typmod as a full 32 bits. Or perhaps it
>> could just be expanded to a signed 64-bit int. What do you think?
>
> Neither i
Jeff Davis writes:
> I haven't looked at all of these places yet, so maybe a few simple
> changes would allow us to treat typmod as a full 32 bits. Or perhaps it
> could just be expanded to a signed 64-bit int. What do you think?
Neither is likely to happen, and even disregarding that, I doubt pe
* Jeff Davis (pg...@j-davis.com) wrote:
> Oid is unsigned, typmod is signed. We might be able to get away with it,
> but -1 is treated specially in some places outside of the type-specific
> functions, e.g. exprTypmod().
Any negative result returned from the input handling function is
considered a
On Fri, 2009-10-30 at 19:12 +0200, Heikki Linnakangas wrote:
> Wait, it doesn't? A typmod is a 32-bit integer, like Oids. Am I missing
> something?
Oid is unsigned, typmod is signed. We might be able to get away with it,
but -1 is treated specially in some places outside of the type-specific
funct
2009/10/30 Heikki Linnakangas :
> Pavel Stehule wrote:
>> 2009/10/30 Heikki Linnakangas :
>>> Pavel Stehule wrote:
else
{
ereport(ERROR,
(errcode(ERRCODE_INVALID_FUNCTION_DEFINITION),
Jeff Davis wrote:
> On Fri, 2009-10-30 at 10:03 +0200, Peter Eisentraut wrote:
>> I can't help but wonder if the period type might better be a generic
>> container for pairs of scalar, totally-ordered types.
>
> That would be ideal. However, it doesn't really look like our type
> system was built
Pavel Stehule wrote:
> 2009/10/30 Heikki Linnakangas :
>> Pavel Stehule wrote:
>>> else
>>> {
>>> ereport(ERROR,
>>> (errcode(ERRCODE_INVALID_FUNCTION_DEFINITION),
>>>errmsg("function result type must be
>>> sp
>> PARTITION BY RANGE ( a_expr )
>> ...
>> PARTITION BY HASH ( a_expr )
>> PARTITIONS num_partitions;
> Unless someone comes up with a maintenance plan for stable hashfunctions, we
> should probably not dare look into this yet.
What would cover the common use case of per-day quals and drops ove
hello ...
as my day has worked out quite nicely up to know i thought to f... it up
and post a new concept which has been requested by a customer. the goal
is to collect some feedback, ideas and so on (not to be mixed up with
"flames").
we have funding for this and we are trying to sort out how
On Fri, 2009-10-30 at 10:03 +0200, Peter Eisentraut wrote:
> I can't help but wonder if the period type might better be a generic
> container for pairs of scalar, totally-ordered types.
That would be ideal. However, it doesn't really look like our type
system was built to handle that kind of thing
2009/10/30 Heikki Linnakangas :
> Pavel Stehule wrote:
>> else
>> {
>> ereport(ERROR,
>> (errcode(ERRCODE_INVALID_FUNCTION_DEFINITION),
>> errmsg("function result type must be
>> specified")));
>>
Developers,
I'm a senior developer for a small Company working on
modifications to both MySQL and PostgreSQL to support better
usage reporting for DBAs. The project is called ExtSQL.
Most of our work was originally done on MySQL and we've
just gotten into PostgreSQL during the last yea
On 10/30/09, Peter Eisentraut wrote:
> Calling PL/Python's elog functions exposes some curious behavior. For
> example, calling plpy.error('foo') prints
>
> ERROR: ('foo',)
>
> (instead of the
>
> ERROR: foo
>
> that one might have hoped for.) This is an implementation artifact,
> becaus
On Fri, 2009-10-30 at 17:55 +0530, shrish purohit wrote:
> Hi,
>
> Updated Kedar's patch sending on behalf of Kedar.
>
> .tar.bz2 file contains files to be put at
> ./src/include/catalog/pg_partition.h
> ./src/backend/utils/partition
> ./src/test/regress/sql/partition.sql
>
> There are not too
Calling PL/Python's elog functions exposes some curious behavior. For
example, calling plpy.error('foo') prints
ERROR: ('foo',)
(instead of the
ERROR: foo
that one might have hoped for.) This is an implementation artifact,
because those functions don't check their arguments, just take them
On Thu, 2009-10-29 at 11:15 +0900, Itagaki Takahiro wrote:
> I'd like to improve partitioning feature in 8.5.
Nice.
> Here is syntax I propose:
Is this the same as / similar to Oracle's syntax?
IIRC Nikhil's patch was Oracle's syntax, and I prefer having that one
instead of inventing our own
Itagaki Takahiro writes:
> Should we have "INHERITS ( parent INCLUDING xxx )" syntax ?
No. That would imply that the user has some control over what is
inherited and what isn't, which would be a complete mess.
regards, tom lane
--
Sent via pgsql-hackers mailing list (p
Pavel Stehule wrote:
> else
> {
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_FUNCTION_DEFINITION),
>errmsg("function result type must be
> specified")));
> /* Alternative possibility: default to RE
On Thu, Oct 29, 2009 at 9:35 AM, Dave Page wrote:
> 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
Hello
I found some strange code. Is code in "ELSE" part dead, or its bug?
if (stmt->returnType)
{
/* explicit RETURNS clause */
compute_return_type(stmt->returnType, languageOid,
&prorettype,
2009/10/27 Andrew Dunstan :
>
>
> Merlin Moncure wrote:
>>
>> On Mon, Oct 26, 2009 at 11:18 PM, Andrew Dunstan
>> wrote:
>>
>>>
>>> Kiswono Prayogo wrote:
>>>
plv8js is a procedural language add-on for PostgreSQL, which means you
can define Javascript functions that run inside a Pos
We have two ways to copy table definitions:
- CREATE TABLE child ( LIKE parent )
- CREATE TABLE child ( ) INHERITS ( parent )
But "INCLUDING xxx" is supported only in "LIKE" version.
Should we have "INHERITS ( parent INCLUDING xxx )" syntax ?
We can use LIKE and INHERITS at once:
CREATE T
On Thu, 2009-10-29 at 15:19 -0700, Jeff Davis wrote:
> I can't help but wonder if the PERIOD type might be better for
> representing a partition range. It would make it easier to express and
> enforce the constraint that no two partition ranges overlap ;)
I can't help but wonder if the period type
31 matches
Mail list logo
