On Mon, 2005-09-05 at 15:38 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
+ /*
+ * If we re-issue an Execute protocol request against an existing
+ * portal, then we are only fetching more rows rather than
+ * completely re-executing the query from the
Simon Riggs wrote:
Looking more closely, I don't think either is correct. Both can be reset
according to rewind operations - see DoPortalRewind().
We'd need to add another bool onto the Portal status data structure.
AFAIK this is only an issue with SCROLLABLE cursors, which v3 portals
On Mon, Sep 05, 2005 at 08:10:16PM +0100, Patrick Welche wrote:
On Mon, Sep 05, 2005 at 03:02:55PM -0400, Tom Lane wrote:
Patrick Welche [EMAIL PROTECTED] writes:
* Allow INET + INT4 to increment the host part of the address, or
throw an error on overflow
I think that the naively
---BeginMessage---
I have been in need of a uuid type and ran across the pguuid download
by Xiongjian (Mike) Wang. This wasn't really useful to me for two
reasons: first, it is GPLed and I would prefer a more liberal license,
secondly, it didn't compile cleanly on Mac OS 10.3, due to lack of a
Hey Nathan.
I've started to make heavy use of pguuid. It had several bugs in it
that required fixing before I could use it. I have no preference on
pguuid. It was the only such PostgreSQL project I found that provided
a UUID type.
I'd be willing to work with you on ensuring that such a patch is
Rafaqat Ali [EMAIL PROTECTED] writes:
Is there any other file in which I have to make change ?
Fooling with any of the bootstrapped catalogs is pretty messy.
You might grab this patch from the CVS server for comparison:
2005-03-29 14:44 tgl
* doc/src/sgml/bki.sgml,
[EMAIL PROTECTED] writes:
My personal preference is that the type be called 'uuid' and accepted
into the core. Tom? Is their history on this issue?
Should it remain an extension, or can be get it built-in?
There is pretty much zero chance of being accepted into contrib, much
less core, if the
On Fri, 2 Sep 2005 15:50:25 -0400
Dave Cramer [EMAIL PROTECTED] wrote:
On 2-Sep-05, at 3:38 PM, Mark Wong wrote:
Hi Dave,
Oops, EJB's are distasteful? My experience in this area is quite
lacking.
Well, I said personally distasteful.
Not that I necessarily want to be 100% strict
On Tue, 2005-08-30 at 00:56 +0200, Martijn van Oosterhout wrote:
I saw the discussion about an tester for MVCC. Since I'd never done
anything with asyncronous queries before, I figured I'd try to write
something useful with it. The result is at:
http://svana.org/kleptog/pgsql/mvcctest.tar.gz
[Please CC any replies, thanks]
I added a field to each of Var, Const, FuncExpr and OpExpr which is set
during parse_expr. But somewhere between the parsing and execution the
values of these fields get reset back to NULL. But only for FuncExpr
and OpExpr, for Var and Const it all works as
On Tue, Sep 06, 2005 at 11:38:57AM -0400, [EMAIL PROTECTED] wrote:
There is pretty much zero chance of being accepted into contrib, much
less core, if the code isn't pure BSD license.
Hmm. Here is the copyright and license portion of the readme...
COPYRIGHT AND LICENSE
Copyright (c)
On Tue, Sep 06, 2005 at 03:51:41PM +, Matt Miller wrote:
On Tue, 2005-08-30 at 00:56 +0200, Martijn van Oosterhout wrote:
http://svana.org/kleptog/pgsql/mvcctest.tar.gz
I've started using it in some simple cases and it seems to be a good
tool. The feature set looks to me to be a pretty
On 6-Sep-05, at 11:37 AM, Mark Wong wrote:
On Fri, 2 Sep 2005 15:50:25 -0400
Dave Cramer [EMAIL PROTECTED] wrote:
On 2-Sep-05, at 3:38 PM, Mark Wong wrote:
Hi Dave,
Oops, EJB's are distasteful? My experience in this area is quite
lacking.
Well, I said personally distasteful.
Not
Tom Lane wrote:
Barring further changes, we'll have a hard-wired template list for
8.1 and a real system catalog in 8.2. So there's a choice now for
PLs that are not part of the core distribution: do you want to be
listed in the hard-wired template?
Is there any way to create the language
Mark,
I suggest that UUID be recommended in place of SERIAL for certain
classes of applications, and that it therefore belongs in the core.
UUID and SERIAL can be used together (although, once you have a UUID,
it may not be useful to also have a SERIAL).
I think that, if you want to push a
Chris Traylor wrote:
Configure options are generally a pain in the neck,
Granted. Especially, if all the ifdefs start making the source hard
to read, but they are a viable compile-time way to allow the user to
make the decision for themselves.
This missing piece of information here is that
Peter Eisentraut [EMAIL PROTECTED] writes:
Is there any way to create the language and not use the template (an
override option of some kind)?
There is deliberately not a way to override (other than using a
different name for the PL). One of the points of this facility is to
fix up broken PL
On Tue, Sep 06, 2005 at 06:06:49PM +0200, Martijn van Oosterhout wrote:
[Please CC any replies, thanks]
I added a field to each of Var, Const, FuncExpr and OpExpr which is set
during parse_expr. But somewhere between the parsing and execution the
values of these fields get reset back to
Tom Lane wrote:
For instance, if you think you might want a validator later,
you can set up a no-op validator procedure today, and then the template
doesn't need to change when you make the validator do something.
Similarly, you could future-proof yourself against adding a trusted (or
Andrew Dunstan wrote:
Anyway, clearly there are cases where a validator make no sense or
very little sense (pl/sh and pl/{j,java} spring to mind).
PL/sh has a validator. :-)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
Tom Lane wrote:
There is deliberately not a way to override (other than using a
different name for the PL). One of the points of this facility is to
fix up broken PL definitions being imported from old dump files, so
believing what the CREATE LANGUAGE command says is exactly what we
don't
Peter Eisentraut [EMAIL PROTECTED] writes:
I don't doubt that, but I just have a stomach ache with this entire
notion of having a hard-coded exception list of the sort if the user
requires this, do this instead.
I don't see it as an exception list. The direction I see for this is
that the
Peter Eisentraut wrote:
Andrew Dunstan wrote:
Anyway, clearly there are cases where a validator make no sense or
very little sense (pl/sh and pl/{j,java} spring to mind).
PL/sh has a validator. :-)
Really? Curious. I must look more closely.
cheers
andrew
Tom Lane wrote:
I don't see it as an exception list. The direction I see for this is
that the parameters to CREATE LANGUAGE are obsolete and will
eventually be removed altogether, with CREATE LANGUAGE foo using an
existing template as the only recommended way to do it.
So your proposal is to
Martijn van Oosterhout kleptog@svana.org writes:
grep reveals several places where new nodes are created but rather than
just changing them all, is there a particular phase where these changes
are made that I should be looking at?
Grepping for makeNode(OpExpr) might help you. Offhand I'd
Peter Eisentraut [EMAIL PROTECTED] writes:
So your proposal is to enable a new language by doing:
1. register a template
2. activate template using CREATE LANGUAGE (which would copy it to
pg_language)
That's the long-term idea, yes.
How is this different from
1. register language in
On Tue, Sep 06, 2005 at 01:51:25PM -0400, Tom Lane wrote:
Grepping for makeNode(OpExpr) might help you. Offhand I'd finger
eval_const_expressions as the likely culprit. clauses.c has some other
code you'd better look at too.
Yeah, eval_const_expressions was the culprit in this case, though I
i am using postgresql 8.0.3 as a single user by running postgres
I want to purge all contents in the bufferpool, and I did this by
calling InitBufTable(256) (buf_table.c) after each query. However,
this seems not working for each followup query I still get less disk read
(tracked by smgrread()
On Tue, Sep 06, 2005 at 06:21:11PM +0200, Martijn van Oosterhout wrote:
On Tue, Sep 06, 2005 at 03:51:41PM +, Matt Miller wrote:
On Tue, 2005-08-30 at 00:56 +0200, Martijn van Oosterhout wrote:
http://svana.org/kleptog/pgsql/mvcctest.tar.gz
I've started using it in some simple cases
FWIW, I think a lot of people didn't me too on all the features they
want, so I wouldn't put too much weight on the ranking here...
On Mon, Sep 05, 2005 at 05:43:16PM +0200, Peter Eisentraut wrote:
Am Freitag, 26. August 2005 01:13 schrieb Alvaro Herrera:
Or, slightly different, what are
not sure where to put this.
I run two queries:
1. select count(*) from table where indexed_column10;
2. select * from table where indexed_column10;
the indexed column is not clustered at all. I saw from the trace that
both query runs
through index scans on that index and takes the same amount
huaxin... I'll save you the time... see the topic MUCH ADO ABOUT COUNT(*) and ADVANCED INDEX USAGE.
On 9/6/05, huaxin zhang [EMAIL PROTECTED] wrote:
not sure where to put this.I run two queries:1. select count(*) from table where indexed_column10;2. select * from table where indexed_column10;the
On Tue, Sep 06, 2005 at 15:21:16 -0400,
huaxin zhang [EMAIL PROTECTED] wrote:
not sure where to put this.
I run two queries:
1. select count(*) from table where indexed_column10;
2. select * from table where indexed_column10;
the indexed column is not clustered at all. I saw from
Hi there,
after we have GiST with concurrency and recovery support
(thanks to PosGIS community for support) I'd trying to
find info about level of extensibility support in
other major RDBMS's like Relational Extenders of DB2,
Cartridges in Oracle and (?) in MS SQL.
With current GiST one
I agree with Josh on the UUID type, it gets abused far too often and
(IMHO) isn't widely enough used to belong in the core. Couldn't you just fix the problem in
pguuid rather than write a whole new type?On 9/6/05, Josh Berkus josh@agliodbs.com wrote:
Mark, I suggest that UUID be recommended in
On Tue, Sep 06, 2005 at 03:57:55PM -0400, [EMAIL PROTECTED] wrote:
I agree with Josh on the UUID type, it gets abused far too often
Out of curiosity, how does it get abused? It doesn't seem to me
that it would be any more prone to abuse than any other type.
and (IMHO) isn't widely enough used
I didn't see anything mentioned in the docs about this, so I'm curious
as to how significant of a change you can make to the hardware or
software configuration for a restore before breaking things.
Secondly, is PostgreSQL smart enough to complain in these cases or will
it be silent and cause
On Sep 6, 2005, at 12:57 PM, Jonah H. Harris wrote:On 9/6/05, Josh Berkus josh@agliodbs.com wrote: Mark, I suggest that UUID be recommended in place of SERIAL for certain classes of applications, and that it therefore belongs in the core. UUID and SERIAL can be used together (although, once you
The only time I've seen someone use UUIDs in PostgreSQL is when they
were converting from SQL Server. I've seen many bad data models
using UUID that could've/should've used normal sequences for
portability.
I look forward to seeing you're code.
Thanks!
On 9/6/05, nathan wagner [EMAIL PROTECTED]
huaxin zhang [EMAIL PROTECTED] writes:
I want to purge all contents in the bufferpool,
Why do you think that's a good idea? It certainly won't purge the
kernel's disk caches, so if you're hoping to restore the system to
ground zero this won't do it.
and I did this by
calling
On Tue, Sep 06, 2005 at 03:57:55PM -0400, Jonah H. Harris wrote:
I agree with Josh on the UUID type, it gets abused far too often and (IMHO)
isn't widely enough used to belong in the core.
There is much in PostgreSQL from my perspective that falls under the
category of 'most advanced open
On Tue, Sep 06, 2005 at 09:16:13PM +, nathan wagner wrote:
On Tue, Sep 06, 2005 at 03:57:55PM -0400, [EMAIL PROTECTED] wrote:
I agree with Josh on the UUID type, it gets abused far too often
Out of curiosity, how does it get abused? It doesn't seem to me
that it would be any more prone
Rod Taylor [EMAIL PROTECTED] writes:
Secondly, is PostgreSQL smart enough to complain in these cases or will
it be silent and cause unexpected data corruption later on?
It will catch anything that affects the contents or layout of
pg_control, which includes a fair amount of stuff (endianness,
[EMAIL PROTECTED] (huaxin zhang) writes:
not sure where to put this.
I run two queries:
1. select count(*) from table where indexed_column10;
2. select * from table where indexed_column10;
the indexed column is not clustered at all. I saw from the trace
that both query runs through
On Tue, Sep 06, 2005 at 11:52:18PM +0400, Oleg Bartunov wrote:
btw, GiST programming tutorial is available in Russian,
http://www.sai.msu.su/~megera/postgres/talks/gist_tutorial.html
Cool. Is an English version in the works?
--
Michael Fuhr
---(end of
On Fri, Sep 02, 2005 at 03:51:15PM -0400, Bruce Momjian wrote:
One possible solution is to create a phantom cid which represents a
cmin/cmax pair and is stored in local memory.
If we're going to look at doing that I think it would also be good to
consider including xmin and xmax
On Sep 6, 2005, at 2:16 PM, nathan wagner wrote:
On Tue, Sep 06, 2005 at 03:57:55PM -0400, [EMAIL PROTECTED]
wrote:
I agree with Josh on the UUID type, it gets abused far too often
Out of curiosity, how does it get abused? It doesn't seem to me
that it would be any more prone to abuse
On Tue, 2005-09-06 at 16:53 -0400, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Secondly, is PostgreSQL smart enough to complain in these cases or will
it be silent and cause unexpected data corruption later on?
It will catch anything that affects the contents or layout of
On Tue, Sep 06, 2005 at 01:49:28PM -0700, David Fetter wrote:
On Tue, Sep 06, 2005 at 09:16:13PM +, nathan wagner wrote:
On Tue, Sep 06, 2005 at 03:57:55PM -0400, [EMAIL PROTECTED] wrote:
I agree with Josh on the UUID type, it gets abused far too often
Out of curiosity, how does it get
On Tue, Sep 06, 2005 at 03:58:28PM -0500, Jim C. Nasby wrote:
On Fri, Sep 02, 2005 at 03:51:15PM -0400, Bruce Momjian wrote:
One possible solution is to create a phantom cid which represents a
cmin/cmax pair and is stored in local memory.
If we're going to look at doing that I
[EMAIL PROTECTED] writes:
In my choice of use, I'm using them instead of SERIAL columns, as I
wish to have more freedom merging production data with test data. I
wish to continually import production data into my test environment,
in a single direction. UUID will prevent conflicts from
[EMAIL PROTECTED] writes:
Personally, I'm not sure what the big opposition to UUID is all about.
I don't see any big opposition. People are simply questioning the
idea whether it belongs in core PG. The reason we don't want to accept
everything-and-the-kitchen-sink in core is that we have only
On Tue, Sep 06, 2005 at 05:37:06PM -0400, Alvaro Herrera wrote:
On Tue, Sep 06, 2005 at 03:58:28PM -0500, Jim C. Nasby wrote:
On Fri, Sep 02, 2005 at 03:51:15PM -0400, Bruce Momjian wrote:
One possible solution is to create a phantom cid which represents a
cmin/cmax pair and is
Jim C. Nasby [EMAIL PROTECTED] writes:
If we're going to look at doing that I think it would also be good to
consider including xmin and xmax as well.
If you do that, you'll never be able to delete or update the tuple.
My idea was to use an int to represent combinations of (c|x)(min|max),
On Tue, Sep 06, 2005 at 05:31:43PM -0400, Greg Stark wrote:
Just do something like this for every sequence:
ALTER SEQUENCE foo INCREMENT BY 100
And then choose a particular initial value for each server.
*shudder*
But you are right. That would work. :-) (I shudder from the maintenance
On Tue, Sep 06, 2005 at 05:54:34PM -0400, Tom Lane wrote:
I don't see any big opposition. People are simply questioning the
idea whether it belongs in core PG. The reason we don't want to accept
everything-and-the-kitchen-sink in core is that we have only limited
manpower to maintain it. So
As promised a link to the code.
http://granicus.if.org/~nw/ossp_pg_uuid-0.1.tar.gz
You'll also need Ralf Engelschall's uuid library, which mine is a postgres
interface to. It's available at
ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.3.0.tar.gz
It probably has a few warts. I'm mainly posting it
On Tue, Sep 06, 2005 at 05:54:34PM -0400, [EMAIL PROTECTED] wrote:
One thing that is raising my own level of concern quite a bit is the
apparent portability issues.
I can't speak to the portability in general, but there is a PORTING file
in the ossp uuid library that states
OSSP uuid was
On Tue, Sep 06, 2005 at 06:02:27PM -0400, Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
If we're going to look at doing that I think it would also be good to
consider including xmin and xmax as well.
If you do that, you'll never be able to delete or update the tuple.
My idea
Jim C. Nasby [EMAIL PROTECTED] writes:
If the 4 header fields in question were just normalized out, wouldn't
all the semantics continue to work the same? All I'm envisioning is
replacing them in each tuple with a pointer (vis_id) to another
datastore that would be roughly equivalent to:
On Sep 6, 2005, at 3:06 PM, [EMAIL PROTECTED] wrote:
On Tue, Sep 06, 2005 at 05:54:34PM -0400, Tom Lane wrote:
I don't see any big opposition. People are simply questioning the
idea whether it belongs in core PG. The reason we don't want to
accept
everything-and-the-kitchen-sink in core
Tom, you worded my thoughts much better than I did.
Bob, I too had heard that host-based UUIDs/GUIDs had issues with
uniqueness. I think Microsoft's implementation was hosed and they
ended up eliminating using the MAC completely.
I'll check out the code get back.
On 9/6/05, Bob Ippolito [EMAIL
[EMAIL PROTECTED] writes:
Eventually, SERIAL wraps around. So you switch to SERIAL8. At the point that
you have SERIAL8, you aren't worried terribly about disk space, and you
realize there is usually no benefit at all to the numbers being ordered so
closely.
a) Except for trivially small
adey [EMAIL PROTECTED] writes:
Please let me know if there is a way to determine when the Postmaster was
last restarted?
The last postmaster start time, or the last database reset? These are
not the same if any backends have crashed since the postmaster started.
For determining stats lifespan
Bob, People,
Let me clarify my stance here, because it seems to be getting
misrepresented.
Mark (and Nathan) pushed at repaired UUID type for possible inclusion in
the core PostgreSQL distribution. I'm not opposed to that, provided that
the portability, licensing, and bugs are worked out.
On Sep 6, 2005, at 6:02 PM, Josh Berkus wrote:
Bob, People,
Let me clarify my stance here, because it seems to be getting
misrepresented.
Mark (and Nathan) pushed at repaired UUID type for possible
inclusion in
the core PostgreSQL distribution. I'm not opposed to that,
provided that
the
On Tue, Sep 06, 2005 at 06:02:50PM -0700, Josh Berkus wrote:
However, Mark went on to suggest that we should recommend UUID over SERIAL
in the docs, and that we could consider dropping SERIAL entirely in favor
of UUID:
---quoth Mark--
I suggest that UUID be recommended in
Mark,
I agree. Although I lost it on the cannot be normalized. I'm assuming
there are designs you have seen much worse than the ones I have seen.
:-)
Mostly it's the problem of tables that don't have a real key, only a
surrogate key. How do you know what's a duplicate?
For my part, I
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf Of Josh Berkus
Sent: Tuesday, September 06, 2005 6:40 PM
To: [EMAIL PROTECTED]
Cc: Bob Ippolito; [EMAIL PROTECTED];
pgsql-hackers@postgresql.org;
nathan wagner
Subject: Re: [HACKERS] uuid
On Tue, Sep 06, 2005 at 06:40:27PM -0700, josh@agliodbs.com wrote:
Sure. What's a UUID, after all? It's three pieces of information:
1) A server or database instance identifier
2) A table identifier
3) A row identifier
e.g.:
chayote.sf.agliodbs.com | public.customers | 4271
On 2005-09-06, Patrick Welche [EMAIL PROTECTED] wrote:
Now with:
test=# select '192.168.0.0/24'::inet + 1;
ERROR: Trying to increment a network (192.168.0.0/24) rather than a host
What possible justification is there for this behaviour?
test=# select '192.168.0.1/24'::inet + -1;
ERROR:
Peter Eisentraut wrote:
Chris Traylor wrote:
Configure options are generally a pain in the neck,
Granted. Especially, if all the ifdefs start making the source hard
to read, but they are a viable compile-time way to allow the user to
make the decision for themselves.
This missing piece of
Just an FYI:
We also ended up rolling our own uuid type, against libuuid. It
seems that uuid is a widespread enough concept that implementors
*will* be asked to support it, moderately often. We *could* roll our
own (were capable), others are not so lucky, and would have to point
out
Paul Ramsey [EMAIL PROTECTED] writes:
I am not sure if I heard clearly from the core team that a self-
contained, BSD-licensed uuid would be accepted(able)?
I don't think any of the other core members weighed in on this thread,
so speaking strictly for myself: BSD license is an issue, and
On Tue, 6 Sep 2005, Michael Fuhr wrote:
On Tue, Sep 06, 2005 at 11:52:18PM +0400, Oleg Bartunov wrote:
btw, GiST programming tutorial is available in Russian,
http://www.sai.msu.su/~megera/postgres/talks/gist_tutorial.html
Cool. Is an English version in the works?
I was optimistic when I
On Tue, Sep 06, 2005 at 08:40:08PM -0700, [EMAIL PROTECTED] wrote:
- linking against libuuid is fine for a contrib/ extension, but no
good for a built-in type. A real uuid would have to do a proper
independent implementation of uuid creation within pgsql.
Why?
I'm not sure what the
On Tue, Sep 06, 2005 at 07:02:20PM -0400, Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
If the 4 header fields in question were just normalized out, wouldn't
all the semantics continue to work the same? All I'm envisioning is
replacing them in each tuple with a pointer (vis_id) to
Tom,
I assume that the path of the shared library will be somehow relative to
the GUC dynamic_library_path? If not, the lanlibrary should be changed
to $libdir/libpljava. That requires that PL/Java is installed within
the PostgreSQL distribution.
I also assume that the handler name can be
On Tue, Sep 06, 2005 at 08:22:34PM -0400, Tom Lane wrote:
PG 8.1 will have a function to return postmaster start time, but not
database reset time. I wonder if this is misdefined --- if you are
trying to measure database uptime, the last reset would be more
appropriate to track.
Is it too
79 matches
Mail list logo
