Hello,
I miss some info in context: function's oid, function's argumenst and
schema. Maybe:
199292 function public.foo(int, int, int) language plpgsql statement return
line 10
or short version:
1229298 function public.foo 10 return which is easy parseable
Best regards
Pavel
Attached patch adds a version check for bison when running the
vc++
build.
Shouldn't it be looking for 2.1 as well?
2.1 is the broken one.
Exactly. So we should reject it.
We do. The code as-is *only* accepts 1.875. Thus it rejects 2.1.
//Magnus
---(end
The stylesheet (/css/cvsweb/cvsweb.css) is a 404, that's why.
I don't really know my way around that box, so I don't know why it
happened and what to fix, but that's what's broken.
//Magnus
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
[EMAIL PROTECTED] On Behalf
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Magnus Hagander
Sent: 04 October 2006 08:36
To: Andrew Dunstan; PostgreSQL Hackers
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] cvsweb.cgi missing colors
The stylesheet
So basically, glibc's qsort is bad enough that even a
10%-more-comparisons advantage doesn't save it.
Do those numbers look very different if you have lots of
columns or if you're sorting on something like an array or a ROW?
Imho, that also is an argument for using our own qsort.
It can
Simon,
We have almost everything you listed in our TODO
http://www.sai.msu.su/~megera/wiki/todo
btw, there is gendict subdirectory, which help people to generate
dictionaries (including snowball stemmers) for tsearch2.
Oleg
On Tue, 3 Oct 2006, Simon Riggs wrote:
I'm looking at some of
Bruce Momjian wrote:
Zdenek Kotala wrote:
Solaris had broken strtod function when parse Inf and Nan. See
solaris.h. This bug has been fixed for all current versions of Solaris (
8, 9, 10). See
http://sunsolve.sun.com/search/document.do?assetkey=1-21-108993-62-1searchclause=108993-62
In gram.y
Typename: SimpleTypename opt_array_bounds
{
$$ = $1;
$$-arrayBounds = $2;
}
| SETOF SimpleTypename opt_array_bounds
{
$$ = $2;
$$-arrayBounds =
On Tue, Oct 03, 2006 at 08:26:36PM -0400, Bruce Momjian wrote:
I have run pgindent for 8.2.
Is there a way to make pgindent skip a directory? It seems it has
changed all expected file in ecpg's regression suite. So we see a lot of
differences now.
Michael
--
Michael Meskes
Email: Michael at
Hi, Tom,
Tom Lane wrote:
Here's a small patch that adds an appropriate explanation.
If we're going to document these aliases, what of float4, float8, and bool?
Also, although the docs mention int2/int4/int8, it's more or less left
to the reader's imagination to deduce what they are.
On Tue, Oct 03, 2006 at 05:27:31PM -0400, Andrew Dunstan wrote:
It is surely not the only memory leak. We know there are some and in
most cases (like this) they aren't worth the trouble to clean up. If it
were used in psql or the backend I'd be worried, but it isn't, so I'm not.
Ofcourse
Hi, Tom,
Tom Lane wrote:
No, it should be something like
syntax error in tsearch query: contents of string
since it's not always the case that you know exactly what string got fed
to to_tsquery().
I agree.
It's also possible that you have more than one tsearch expression in the
On Tue, Oct 03, 2006 at 06:54:15PM -0400, Tom Lane wrote:
Looks like blow-back from the recent change in default GUC parameters.
However, I think update the expected output is the wrong answer,
I completely agree and thus changed this example to only show variable
settings of variable the
Magnus Hagander wrote:
Attached patch adds a version check for bison when running the
vc++
build.
Shouldn't it be looking for 2.1 as well?
2.1 is the broken one.
Exactly. So we should reject it.
We do. The code as-is *only* accepts 1.875. Thus it rejects 2.1.
I think
Michael Meskes wrote:
On Tue, Oct 03, 2006 at 08:26:36PM -0400, Bruce Momjian wrote:
I have run pgindent for 8.2.
Is there a way to make pgindent skip a directory? It seems it has
changed all expected file in ecpg's regression suite. So we see a lot of
differences now.
Sure a directory
On Wed, Oct 04, 2006 at 06:15:31AM -0400, Bruce Momjian wrote:
Michael Meskes wrote:
Is there a way to make pgindent skip a directory? It seems it has
changed all expected file in ecpg's regression suite. So we see a lot of
differences now.
Sure a directory can be skipped. I am confused
Just to let everyone know, I'm continuing work on the Block B-tree idea
discussed earlier.
The current plan is to have a (compressed) bitmap of offsets attached to
index tuples, to allow vacuuming. For example, if we have a heap like this:
2
4
6
8
-
10
12
14
16
5
-
18
20
where dashes
I'm not sure this is the right group to ask this. I see that the 8.2
notes say all SQL:2003 statistical functions are implemented in 8.2, but
I couldn't find a listing for those anywhere I looked.
For those who are clueless like me, can someone provide a listing of
what these functions are?
Zdenek Kotala wrote:
Alvaro Herrera wrote:
What's global? A maybe-useful flag would be telling that a table is
shared. Is that it? Mind you, it's not useful to me because I know
which tables are shared, but I guess for someone not so familiar with
the catalogs it could have some use.
Would it be possible to move the whole crtdefs.h block
into win32.h?
Nope, it needs to go before stdio.h and friends, unfortunatly.
OK, patch committed as-is then. The whole thing still looks
awfully icky though, particularly the way pg_config_os.h is
included in one place for
2.1 is the broken one.
Exactly. So we should reject it.
We do. The code as-is *only* accepts 1.875. Thus it rejects 2.1.
I think Tom's point is that we should reject only 2.1. Isn't
that the only version that fails?
Not entirely sure. I beleive there were older versions
And given that, they're going to get the latest by default, or
1.875
if they read the (currently being written) README.
The point was, that = 2.2 won't be allowed when it comes out for
win32, even if it should work.
Right. So I'd update it once we see a working version other than 1.875.
On 10/4/06, Obe, Regina [EMAIL PROTECTED] wrote:
I'm not sure this is the right group to ask this. I see that the 8.2
notes say all SQL:2003 statistical functions are implemented in 8.2, but
I couldn't find a listing for those anywhere I looked.
For those who are clueless like me, can someone
Markus Schaber wrote:
It's not only about documenting the pure existence of the aliases (which
was already documented in the table on the datatype TOC page), it's also
about telling the user which of the names are the ones to avoid, and the
reasons to do so.
*blink* Why do any need to be
Zdenek Kotala [EMAIL PROTECTED] writes:
There is new version of catalogs overview patch. This version add only
one column into overview table which contains Oid/Filename for each
catalog table. Oid information is important if someone need make
relation with filename on disk and related
Magnus Hagander [EMAIL PROTECTED] writes:
The point was, that = 2.2 won't be allowed when it comes out for
win32, even if it should work.
Right. So I'd update it once we see a working version other than 1.875.
No, we should ship it that way to start with. Otherwise we're going to
get caught
The point was, that = 2.2 won't be allowed when it comes out
for
win32, even if it should work.
Right. So I'd update it once we see a working version other than
1.875.
No, we should ship it that way to start with. Otherwise we're
going to get caught with no released source code that
Magnus Hagander [EMAIL PROTECTED] writes:
I think Tom's point is that we should reject only 2.1. Isn't
that the only version that fails?
Not entirely sure. I beleive there were older versions that don't work
as well...
My recollection is that the version immediately prior to 1.875 was
Magnus Hagander [EMAIL PROTECTED] writes:
Ok. So what you want is something that checks that it's =1.875 but
specifically not 2.1?
Let me finish investigating the 2.x series and get back to you on that.
Might be a while before I can submit an updated patch for that, may need
to rewrite the
I wrote:
Let me finish investigating the 2.x series and get back to you on that.
2.1 indeed seems to be the only version that emits the busted semicolon.
I found that 2.2 and 2.3 both fail one of their make check tests on my
machine --- if that's widespread it might explain a slow uptake rate
Hi, Andrew,
Andrew Dunstan wrote:
It's not only about documenting the pure existence of the aliases (which
was already documented in the table on the datatype TOC page), it's also
about telling the user which of the names are the ones to avoid, and the
reasons to do so.
*blink* Why do any
Ok. So what you want is something that checks that it's
=1.875 but specifically not 2.1?
Might be a while before I can submit an updated patch for
that, may need to rewrite the whole script in perl to do that
:-( .bat files are horribly limited in what they can do.
Since we are on NT
Ok. So what you want is something that checks that it's
=1.875 but specifically not 2.1?
Might be a while before I can submit an updated patch for that,
may
need to rewrite the whole script in perl to do that :-( .bat
files are
horribly limited in what they can do.
Since we are on
-Original Message-
From: Magnus Hagander [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 04, 2006 6:01 PM
To: Zeugswetter Andreas ADI SD
Cc: pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] [PATCHES] vcbuild bison check
Ok. So what you want is something that checks
Magnus Hagander wrote:
Ok. So what you want is something that checks that it's
=1.875 but specifically not 2.1?
Might be a while before I can submit an updated patch for that,
may
need to rewrite the whole script in perl to do that :-( .bat
files are
And given that, they're going to get the latest by default,
or 1.875 if they read the (currently being written) README.
The point was, that = 2.2 won't be allowed when it comes out for win32,
even if it should work.
Andreas
---(end of
Pavel Stehule [EMAIL PROTECTED] writes:
I miss some info in context: function's oid, function's argumenst and
schema. Maybe:
199292 function public.foo(int, int, int) language plpgsql statement return
line 10
Putting the OID there is a seriously awful idea, not least because it
would make
We were just analyzing some more OProfile and ltrace data against
Postgres 8.2Beta1 and we noticed a number of calls as follows:
strlen(postgres: tpc tpc 192.168.1.200(...)= 58
memset(0xb6b2, '\000', 2344) = 0xb6b2
We have tracked this down to the following code in
Teodor Sigaev [EMAIL PROTECTED] writes:
May I eliminate SETOF from Typename and leave it
only for RETURNS?
Why do you want to?
I think the reason it's in Typename is the assumption that in future
we would try to extend the applicability of SETOF, not restrict it.
For instance I can see
Magnus Hagander [EMAIL PROTECTED] writes:
See attached patch.
Grumble. That's going to be a continuing maintenance pain, isn't it?
We need to find a way to extract the list from the src/port Makefile.
regards, tom lane
---(end of
Hi, Tom,
Tom Lane wrote:
I miss some info in context: function's oid, function's argumenst and
schema. Maybe:
199292 function public.foo(int, int, int) language plpgsql statement return
line 10
Putting the OID there is a seriously awful idea, not least because it
would make it
See attached patch.
Grumble. That's going to be a continuing maintenance pain, isn't
it?
We need to find a way to extract the list from the src/port
Makefile.
Well, it's platform dependent as it's set from configure, no?
I guess we could pull the use on all platforms set, and then just
Why do you want to?
Just simplify.
For instance I can see reasons for wanting SETOF on a function's input
parameter (to pass it a whole table or select result in one call).
I see. But Typename is used for table's definition for example. I can't imagine
column setof text.
--
Teodor
Magnus Hagander [EMAIL PROTECTED] writes:
I guess we could pull the use on all platforms set, and then just
append win32 specific ones, that should help a bit? If there is such a
list (don't have the code around right now) to read from.
That would probably help. Currently the all platforms
Teodor Sigaev [EMAIL PROTECTED] writes:
Why do you want to?
Just simplify.
I think you'd just be moving the complexity somewhere else.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner
ZA == Zeugswetter Andreas DCP SD [EMAIL PROTECTED] writes:
ZA Yes, but it obviously does not in some ports, and that was the
ZA main problem as I interpreted it.
strncpy is part of POSIX; I highly doubt anyone gets it wrong. Getting
sane semantics from it does require manually writing null to
Tom Lane wrote:
Zdenek Kotala [EMAIL PROTECTED] writes:
There is new version of catalogs overview patch. This version add only
one column into overview table which contains Oid/Filename for each
catalog table. Oid information is important if someone need make
relation with filename on disk
I updated FAQ_Solaris. I added new information related to Solaris 10,
rewrote optimalization hints and add information about dtrace. I talked
with Peter about Current maintainer role, and he said that this
information says anything and should be deleted.
Please, let me know your
I signed up for the Netflix Prize. (www.netflixprize.com) and downloaded
their data and have imported it into PostgreSQL. Here is how I created the
table:
Table public.ratings
Column | Type | Modifiers
+-+---
item | integer |
client | integer |
rating | integer
Joachim Wieland wrote:
On Wed, Oct 04, 2006 at 06:15:31AM -0400, Bruce Momjian wrote:
Michael Meskes wrote:
Is there a way to make pgindent skip a directory? It seems it has
changed all expected file in ecpg's regression suite. So we see a lot of
differences now.
Sure a directory
Mark,
On 10/4/06 1:43 PM, Mark Woodward [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:~/netflix$ time psql netflix -c select count(*) from
ratings
count
---
100480507
(1 row)
real2m6.270s
user0m0.004s
sys 0m0.005s
I think you are getting about 40MB/s on your
Mark Woodward [EMAIL PROTECTED] writes:
The one thing I notice is that it is REAL slow.
How fast is your disk? Counting on my fingers, I estimate you are
scanning the table at about 47MB/sec, which might or might not be
disk-limited...
I'm using 8.1.4. The rdate field looks something like:
Merlin Moncure wrote:
On 10/4/06, Obe, Regina [EMAIL PROTECTED] wrote:
I'm not sure this is the right group to ask this. I see that the 8.2
notes say all SQL:2003 statistical functions are implemented in 8.2, but
I couldn't find a listing for those anywhere I looked.
For those who are
Mark Woodward [EMAIL PROTECTED] writes:
I'm using 8.1.4. The rdate field looks something like: 2005-09-06 So,
the raw data is 23 bytes, the date string will probably be rounded up to
12 bytes, that's 24 bytes per row of data. What is the overhead per
variable? per row?
Is there any
Pavel Stehule [EMAIL PROTECTED] writes:
I miss some info in context: function's oid, function's argumenst and
schema. Maybe:
199292 function public.foo(int, int, int) language plpgsql statement
return
line 10
Putting the OID there is a seriously awful idea, not least because it
would
On Sun, 1 Oct 2006, Tom Lane wrote:
Does this version of the patch address your concerns.
Some searching of the net shows that this has been reported before. Once in
the beta for 8.1 and again in January as bug #2192 (It looks like a patch
was included then but wasn't applied).
It seems
Patch applied. Thanks.
---
Zdenek Kotala wrote:
I updated FAQ_Solaris. I added new information related to Solaris 10,
rewrote optimalization hints and add information about dtrace. I talked
with Peter about Current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I signed up for the Netflix Prize. (www.netflixprize.com)
and downloaded their data and have imported it into PostgreSQL.
Here is how I created the table:
I signed up as well, but have the table as follows:
CREATE TABLE rating (
movie
Zdenek Kotala wrote:
Bruce Momjian wrote:
Zdenek Kotala wrote:
Solaris had broken strtod function when parse Inf and Nan. See
solaris.h. This bug has been fixed for all current versions of Solaris (
8, 9, 10). See
I signed up for the Netflix Prize. (www.netflixprize.com)
and downloaded their data and have imported it into PostgreSQL.
Here is how I created the table:
I signed up as well, but have the table as follows:
CREATE TABLE rating (
movie SMALLINT NOT NULL,
person INTEGER NOT NULL,
Mark Woodward [EMAIL PROTECTED] writes:
The one thing I notice is that it is REAL slow.
How fast is your disk? Counting on my fingers, I estimate you are
scanning the table at about 47MB/sec, which might or might not be
disk-limited...
I'm using 8.1.4. The rdate field looks something
Greg Sabino Mullane [EMAIL PROTECTED] writes:
CREATE TABLE rating (
movie SMALLINT NOT NULL,
person INTEGER NOT NULL,
rating SMALLINT NOT NULL,
viewed DATE NOT NULL
);
You would probably be better off putting the two smallints first followed by
the integer and date.
Zdenek, Bruce,
Has anyone updated the Solaris portion of runtime.sgml yet?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Greg Sabino Mullane [EMAIL PROTECTED] writes:
CREATE TABLE rating (
movie SMALLINT NOT NULL,
person INTEGER NOT NULL,
rating SMALLINT NOT NULL,
viewed DATE NOT NULL
);
You would probably be better off putting the two smallints first followed
by
the integer and date.
Mark Woodward [EMAIL PROTECTED] writes:
The rating, however, is one char 1~9. Would making it a char(1) buy anything?
No, that would actually hurt because of the length word for the char
field. Even if you used the char type, which really is only one byte,
you wouldn't win anything because of
Mark Woodward [EMAIL PROTECTED] writes:
The rating, however, is one char 1~9. Would making it a char(1) buy
anything?
No, that would actually hurt because of the length word for the char
field. Even if you used the char type, which really is only one byte,
you wouldn't win anything because
Steve Singer [EMAIL PROTECTED] writes:
Some searching of the net shows that this has been reported before. Once in
the beta for 8.1 and again in January as bug #2192 (It looks like a patch
was included then but wasn't applied).
Yeah, I see that, not sure why we didn't apply that patch.
I've applied the attached patch which merges ideas from your version and
John Jorgensen's. Please check it.
regards, tom lane
*** src/backend/utils/adt/float.c.orig Tue Oct 3 23:16:36 2006
--- src/backend/utils/adt/float.c Wed Oct 4 21:21:17 2006
***
Josh Berkus wrote:
Zdenek, Bruce,
Has anyone updated the Solaris portion of runtime.sgml yet?
No, I was unaware it needed updating.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
To match the description on http://momjian.us/main/writings/pgsql/sgml/explicit-locking.html*** ../../include/storage/lock.h.orig 2006-10-05 00:25:
06.0 -0300--- ../../include/storage/lock.h 2006-10-05 00:31:16.0 -0300** 109,116 #define AccessShareLock 1 /*
On Wed, Oct 04, 2006 at 09:04:11PM +0400, Teodor Sigaev wrote:
Why do you want to?
Just simplify.
For instance I can see reasons for wanting SETOF on a function's
input parameter (to pass it a whole table or select result in one
call).
I see. But Typename is used for table's definition
71 matches
Mail list logo
