Hello,
While setting up a buildfarm installation for cygwin, I've
uncountered the following
regression failure :
float8 ... FAILED
== pgsql.3132/src/test/regress/regression.diffs
*** ./expected/float8-small-is-zero.out Tue Jul 18 09:24:52 2006
---
Marc G. Fournier wrote:
Actually it would be nice to have the not-included PLs present in
src/pl/ as their own directories with a README.TXT containing fetch and
build instructions
So we would have
src/pl/plphp/README.TXT
src/pl/pljava/README.TXT
src/pl/plj/README.TXT
and anybody looking for
On 7/18/06, Bort, Paul [EMAIL PROTECTED] wrote:
Mind you, maybe perl provides emulation for uname?
Not that I know of.
Wouldn't $^0 and $Config{archname} cover quite a few, though?
---(end of broadcast)---
TIP 3: Have you checked our
Hi,
In 8.2 the function tuplestore_gettuple in tuplestore.h is either missing or
deprecated? can someone shed some light on this?
(it appears in the tuplestore.c file and there is no deprecation warning
there)
10x.
--
Regards,
Tzahi.
--
Tzahi Fadida
Blog: http://tzahi.blogsite.org |
If you can open a command shell you can get the OS version with the
'ver' command under Windows:
C:\ver
Microsoft Windows XP [Version 5.1.2600]
How do you do this from a program though. Under UNIX uname() is a
function call as well as a program. It returns the os name,
Katsuhiko Okano wrote:
By PostgreSQL8.2, NUM_SUBTRANS_BUFFERS was changed into 128
and recompile and measured again.
NOT occurrence of CSStorm. The value of WIPS was about 400.
measured again.
not occurrence when measured for 30 minutes.
but occurrence when measured for 3 hours, and 1 hour and
Hi,
I have posted a patch to the CVS head for on-disk bitmap index to
pgsql-patches. If this can get in 8.2, that would be great. Any comments and
suggestions are welcome.
I still need to add several items:
(1) README file in src/backend/access/bitmap.
(2) Bitmap index documentation.
(3) Hiding
On Mon, Jul 17, 2006 at 07:37:41PM -0300, Marc G. Fournier wrote:
Actually it would be nice to have the not-included PLs present in
src/pl/ as their own directories with a README.TXT containing fetch and
build instructions
So we would have
src/pl/plphp/README.TXT
src/pl/pljava/README.TXT
On 17-Jul-06, at 6:37 PM, Marc G. Fournier wrote:
On Tue, 18 Jul 2006, Hannu Krosing wrote:
Ühel kenal päeval, E, 2006-07-17 kell 22:01, kirjutas Martijn van
Oosterhout:
On Mon, Jul 17, 2006 at 12:18:46PM -0400, Andrew Dunstan wrote:
Well, I am not making any promises right now about when
On 7/14/06, Tom Lane [EMAIL PROTECTED] wrote:
[ problems with missing schema in dump ]
No, not one of these things can be blamed on pg_dump.
Ok, its not exactly bug but still a big annoyance that
instead dumping fully qualified names it juggles with
search path. And I'm annoyed as a user
I have completed upgrading the cube codebase to use the V1 call
protocol. However, before I submit a patch I would really like to work
out why I have never been able to get cube to pass installcheck.
This is what I get when I run installcheck on a clean version of 8.1.4
(I get similar results
On 7/14/06, Tom Lane [EMAIL PROTECTED] wrote:
I don't see a strong need for moving pgcrypto into core, and there's at
least one argument against it: if someone needs a crypto-free version of
postgres for use someplace with benighted laws, they would be screwed.
Image of hypothetical evil
-Original Message-
From: Petr Jelinek [mailto:[EMAIL PROTECTED]
Sent: 16 July 2006 18:05
To: Dave Page
Cc: PostgreSQL-development
Subject: Re: Windows buildfarm support, or lack of it
Dave Page wrote:
I have spare licences for most versions of Windows as well,
so if
Andrej Ricnik-Bay wrote:
On 7/18/06, Bort, Paul [EMAIL PROTECTED] wrote:
Mind you, maybe perl provides emulation for uname?
Not that I know of.
Wouldn't $^0 and $Config{archname} cover quite a few, though?
No. As previously explained, these values reflect what was true when and
where
Hi,
I already tried to mail [EMAIL PROTECTED] but my message was stalled.
Version: 8.1.4 (binary for win32)
OS: Windows XP SP2
I type: pg_dump -h localhost -U postgres database_name and there is no
question for the password.
I haven't made changes to pg_hba.conf. I'm logged in as user admin,
Hello everyone, I found something that struck me as odd revolving
around automatic typecasting and coalesce. It appears as though a
timestamp will not automatically be cast to a timestamp if the
timestamp is coalesced. Consider the following example:
= select now()'Jul 14 2006 9:16:47AM';
Tino Wildenhain ha scritto:
http://python.projects.postgresql.org/
This works very well for me - although it needs some more
finish (docs and so on) maybe if more people using it
it can get better.
SRF - even lazy ones (e.g. generators) work nicely there.
Regards
Tino Wildenhain
I have a client with the following EAV inspired schema.
CREATE TABLE many_tables (
table_id text primary key,-- defines which virtual table is
encoded
attribute1 text,
attribute2 text,
attribute3 text,
attribute4 text,
...
);
I'd like to use a mix of constraint
What version of bison do you have?
cheers
andrew
Joshua Reich wrote:
I have completed upgrading the cube codebase to use the V1 call
protocol. However, before I submit a patch I would really like to work
out why I have never been able to get cube to pass installcheck.
This is what I get
Looks like gBorg has gone down...
The Slony-I project does plan to move to pgFoundry, once 1.2 is released...
http://slony-wiki.dbitech.ca/index.php/Move_to_PgFoundry_Checklist
But we need to get to that point (1.2) first. Alas, gBorg being down
today doesn't help :-(.
--
(format nil [EMAIL
I upgraded to the latest version (2.3) as per the warning after running
configure.
Josh
Andrew Dunstan wrote:
What version of bison do you have?
cheers
andrew
Joshua Reich wrote:
I have completed upgrading the cube codebase to use the V1 call
protocol. However, before I submit a patch
Then maybe you need to remove cubeparse.[ch] and try again. Bison
changed the error message from parse error to syntax error in
version 1.875 and it has been the same ever since, AFAIK.
cheers
andrew
Joshua Reich wrote:
I upgraded to the latest version (2.3) as per the warning after
Tzahi Fadida [EMAIL PROTECTED] writes:
In 8.2 the function tuplestore_gettuple in tuplestore.h is either missing or
deprecated? can someone shed some light on this?
You need to switch to using tuplestore_gettupleslot. Note that what
comes back won't have any system columns, because the sort
Katsuhiko Okano [EMAIL PROTECTED] writes:
It does not solve, even if it increases the number of NUM_SUBTRANS_BUFFERS.
The problem was only postponed.
Can you provide a reproducible test case for this?
regards, tom lane
---(end of
Joshua Reich [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
What version of bison do you have?
I upgraded to the latest version (2.3) as per the warning after running
configure.
Better look again, because you definitely seem to be using an old bison
to build cubeparse.c.
Dave Page wrote:
It seems that VMWare are following suit - their entry level VMWare
Server is now free for Windows and Linux :-)
http://www.vmware.com/products/server/
It has been for some time, at least in Beta, so I'm not sure who really
went first.
We should be supplying a
Are you sure you don't have a pgpass file, or the environment variable
PGPASSWORD set?
cheers
andrew
Thomas Bley wrote:
Hi,
I already tried to mail [EMAIL PROTECTED] but my message was
stalled.
Version: 8.1.4 (binary for win32)
OS: Windows XP SP2
I type: pg_dump -h localhost -U
MotherMGA [EMAIL PROTECTED] writes:
= select now()coalesce('Jul 14 2006 9:16:47AM');
The coalesce() function is going to resolve its datatype as text in
this situation, and then text dominates timestamp in the comparison
(ie, the result of now() is coerced to text). When you write
= select
Thomas Bley wrote:
I type: pg_dump -h localhost -U postgres database_name and there is no
question for the password.
Have you created a .pgpass (or whatever the equivilant in the Windows
world is)? That could be supplying the password.
I haven't made changes to pg_hba.conf. I'm logged in as
I just downgraded from 2.3 to 1.875 and rebuilt everything, and now it
works fine.
As per Andrew's previous email, in 2.3 the error messages were changed
from parse error to syntax error, causing the diff to fail.
Josh
Tom Lane wrote:
Joshua Reich [EMAIL PROTECTED] writes:
Andrew Dunstan
Andrew Hammond wrote:
I'm not sure what the default behaviour for local socket connections
is. Perhaps you should add a line to your pg_hba.conf to define a rule
for local socket connections. For example
local all all md5
He's on Windows - no local lines there.
cheers
andrew
Hello Andrew,
Thanks a lot!
There is a pgpass file and it contians the password:
D:\Documents and Settings\admin\Application Data\postgresql\pgpass.conf
My installation is on: D:\Program Files\PostgreSQL\8.1\
Maybe it got automatically created by pgadmin3 ?
Looking into the documentation
I'm having trouble with pgxs and it seems like either it's doing something
actively wrong which defeats the purpose of having pgxs or I'm doing something
wrong in how I'm using it.
I have postgres installed in /usr/local/pgsql in addition to having the debian
packages installed in the usual
There is a pgpass file and it contians the password:
D:\Documents and Settings\admin\Application Data\postgresql\pgpass.conf
My installation is on: D:\Program Files\PostgreSQL\8.1\
Maybe it got automatically created by pgadmin3 ?
I'll bet you're right.
Looking into the documentation
If the use case is people running MySQL dumps, then there will be
millions of values-targetlists in MySQL dumps.
I did some experimentation just now, and could not get mysql to accept a
command longer than about 1 million bytes. It complains about
Got a packet bigger than
Has anyone looked thought about what it would take to get progress bars from
clients like pgadmin? (Or dare I even suggest psql:)
My first thought would be a message like CancelQuery which would cause the
backend to peek into a static data structure and return a message that the
client could
+1
Looked, talked it through, it's a very important feature to BI users.
- Luke
Sent from my GoodLink synchronized handheld (www.good.com)
-Original Message-
From: Gregory Stark [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 02:38 PM Eastern Standard Time
To:
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://archives.postgresql.org/pgsql-www/2006-07/msg00061.php
Yeah. I think the TODO item is intended to point to what is now
Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
On Mon, Jul 17, 2006 at 12:25:09AM -0500, Jaime Casanova wrote:
i found this on the Monitoring section:
o Allow protocol-level BIND parameter values to be logged
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php
Good, added to pginclude/README:
Also, tests should be done with configure settings of --enable-cassert
and EXEC_BACKEND on and off.
I think we had more problems this time just because our code is more
complex.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory Stark
Sent: 18 July 2006 19:36
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] Progress bar updates
For a first cut this data structure could just be a float
between 0 and 1.
Or
Ühel kenal päeval, E, 2006-07-17 kell 23:22, kirjutas Matteo Bertini:
Tino Wildenhain ha scritto:
http://python.projects.postgresql.org/
This works very well for me - although it needs some more
finish (docs and so on) maybe if more people using it
it can get better.
SRF - even lazy
On 7/18/06, Aaron Bono [EMAIL PROTECTED] wrote:
On 18 Jul 2006 09:07:08 -0700, Andrew Hammond
[EMAIL PROTECTED] wrote:
I have a client with the following EAV inspired schema.CREATE TABLE many_tables (table_id text primary key,-- defines which virtual table isencodedattribute1 text,attribute2
If looking at http://www.sai.msu.su/~megera/oddmuse/index.cgi?Hstore the
following is displayed :
-
License
Stable version, included into PostgreSQL distribution, released under BSD
license. Development version, available from this site, released under
Ühel kenal päeval, T, 2006-07-18 kell 16:44, kirjutas Andrew Hammond:
On 7/18/06, Aaron Bono [EMAIL PROTECTED] wrote:
On 18 Jul 2006 09:07:08 -0700, Andrew Hammond
[EMAIL PROTECTED] wrote:
I have a client with the following EAV inspired
Andrew Hammond wrote:
Looking into the documentation delivered with pg (PostgreSQL and
pgAdmin Help) there is a page about the pgpass file,
but there is not hint to environment variable pgpassword or the
pgpass-file on the page of pg_dump, maybe you can add it ?
In the documentation page of psql
from http://dev.mysql.com/doc/refman/4.1/en/blob.html
You can change the message buffer size by changing the value of the
max_allowed_packet variable, but you must do so for both the server and
your client program. For example, both mysql and mysqldump allow you to
change the client-side
Thomas Bley wrote:
+ The .pgpass file will be automatically created if you're using
pgAdmin III with store password being enabled in the connection
settings.
It strikes me that this is actually a bad thing for pgadmin3 to be
doing. It should use its own file, not the deafult location,
or maybe split the file up into sections like this example:
[pgadmin3]
localhost:5432:*:postgres:post
[pg_dump]
[psql]
bye
Thomas
Andrew Dunstan wrote:
Thomas Bley wrote:
+ The .pgpass file will be automatically created if you're using
pgAdmin III with store password being enabled in
Hannu Krosing wrote:
Ühel kenal päeval, T, 2006-07-18 kell 16:44, kirjutas Andrew Hammond:
On 7/18/06, Aaron Bono [EMAIL PROTECTED] wrote:
On 18 Jul 2006 09:07:08 -0700, Andrew Hammond
[EMAIL PROTECTED] wrote:
I have a client with the following EAV
I could really use a --view option to pg_dump (and pg_restore, i
imagine). This would instruct pg_dump to dump just a named view, much
like --table, --trigger, --function, etc. Could this maybe be added to a
todo list?
---(end of broadcast)---
TIP
Ühel kenal päeval, K, 2006-07-19 kell 00:20, kirjutas Hannu Krosing:
Ühel kenal päeval, T, 2006-07-18 kell 16:44, kirjutas Andrew Hammond:
On 7/18/06, Aaron Bono [EMAIL PROTECTED] wrote:
On 18 Jul 2006 09:07:08 -0700, Andrew Hammond
[EMAIL PROTECTED] wrote:
David Fetter wrote:
On Tue, Jul 18, 2006 at 03:20:51PM -0300, Bruce Momjian wrote:
Log Message:
---
Done:
o -Display IN, INOUT, and OUT parameters in \df
Oops! Should I change the patch to say IN when it's an IN parameter?
Right now, it stays silent.
[ Moved to
Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
On Mon, Jul 17, 2006 at 12:25:09AM -0500, Jaime Casanova wrote:
i found this on the Monitoring section:
o Allow protocol-level BIND parameter values to be logged
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php
Bruce Momjian wrote:
David Fetter wrote:
On Tue, Jul 18, 2006 at 03:20:51PM -0300, Bruce Momjian wrote:
Log Message:
---
Done:
o -Display IN, INOUT, and OUT parameters in \df
Oops! Should I change the patch to say IN when it's an IN parameter?
Right now, it
On Tue, Jul 18, 2006 at 06:07:01PM -0400, Bruce Momjian wrote:
David Fetter wrote:
On Tue, Jul 18, 2006 at 03:20:51PM -0300, Bruce Momjian wrote:
Log Message:
---
Done:
o -Display IN, INOUT, and OUT parameters in \df
Oops! Should I change the patch to say
On Tue, Jul 18, 2006 at 02:19:01PM -0400 I heard the voice of
Tom Lane, and lo! it spake thus:
I did some experimentation just now, and could not get mysql to accept a
command longer than about 1 million bytes. It complains about
Got a packet bigger than 'max_allowed_packet' bytes
On Tue, Jul 18, 2006 at 03:48:52PM -0700, Neil Conway wrote:
On Tue, 2006-07-18 at 18:06 -0400, Phil Frost wrote:
I could really use a --view option to pg_dump (and pg_restore, i
imagine).
pg_dump -t view_name will work.
-Neil
Oh, you got me all worked up. I was reading this as a
elein wrote:
pg_dump -t view_name will work.
Oh, you got me all worked up. I was reading this as a way to
dump the CONTENTS of a view not the DEFINITION of a view.
I thought someone sneaked in pg_dump of a query in there.
How would you load such a dump, since views are by default
David Fetter [EMAIL PROTECTED] writes:
On Tue, Jul 18, 2006 at 06:07:01PM -0400, Bruce Momjian wrote:
[ Moved to hackers.] No idea. Comments?
I'm thinking no. Parameters by default are unnamed IN parameters,
so I exposed and marked things which differed from that. :)
I agree; the patch
Gregory Stark wrote:
Has anyone looked thought about what it would take to get progress bars from
clients like pgadmin? (Or dare I even suggest psql:)
Some weeks ago I proposed a PROGRESS parameter for COPY, to enable
progress feedback via notices. tgl thinks nobody needs that...
From: Andrew Dunstan
Thomas Bley wrote:
+ The .pgpass file will be automatically created if you're using
pgAdmin III with store password being enabled in the connection
settings.
It strikes me that this is actually a bad thing for pgadmin3 to be
doing. It should use its own file, not
I mentioned this on -general, I believe, but gborg is on one of our last
FreeBSD 4.x servers right now ... I have to scheduale moving it to the
FreeBSD 6.x machines ... neptune had some problems early this morning, and
the 4.x fsck took 9 @@[EMAIL PROTECTED]@# hours to run ;(
On Tue, 18 Jul
On Tue, 18 Jul 2006, Bruce Momjian wrote:
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://archives.postgresql.org/pgsql-www/2006-07/msg00061.php
Yeah. I think the TODO item is intended to point to what is now
On Tue, 2006-07-18 at 14:35 -0400, Gregory Stark wrote:
My first thought would be a message like CancelQuery which would cause the
backend to peek into a static data structure and return a message that the
client could parse and display something intelligent.
I'm not quite sure what you're
Bruce Momjian wrote:
Mario Weilguni wrote:
Will this patch make it into 8.2?
http://archives.postgresql.org/pgsql-patches/2004-12/msg00228.php
It's a really nice feature, would be extremly useful with tools like pgpool.
No, it will not because RESET CONNECTION can mess up interface
Tatsuo Ishii [EMAIL PROTECTED] writes:
Because we don't have control over the email contents (think Google), I
don't think we can renumber old email items without a continual stream
of complaints from users.
I always wonder why we don't add a unique id to each email message
itself.
But that
On Tue, 2006-07-18 at 18:06 -0400, Phil Frost wrote:
I could really use a --view option to pg_dump (and pg_restore, i
imagine).
pg_dump -t view_name will work.
-Neil
---(end of broadcast)---
TIP 6: explain analyze is your friend
Neil Conway [EMAIL PROTECTED] writes:
I'm not quite sure what you're suggesting; presumably you'd need to open
another client connection to send the status report message to a
backend (since a backend will not be polling its input socket during
query execution). That just seems like the wrong
Magnus Hagander [EMAIL PROTECTED] writes:
Per discussion at the conference:
In order to run the regression tests on Windows without msys, pg_regress
needs to be reimplemnted in C.
Patch committed after significant further work. As committed,
pg_regress.c is pretty nearly an exact replacement
I did some experimentation just now, and could not get mysql to accept a
command longer than about 1 million bytes. It complains about
Got a packet bigger than 'max_allowed_packet' bytes
which seems a bit odd because max_allowed_packet is allegedly set to
16 million, but anyway I don't think
I did some experimentation just now, and could not get mysql to accept a
command longer than about 1 million bytes. It complains about
Got a packet bigger than 'max_allowed_packet' bytes
which seems a bit odd because max_allowed_packet is allegedly set to
16 million, but anyway I don't think
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Strange. Last time I checked I thought MySQL dump used 'multivalue
lists in inserts' for dumps, for the same reason that we use COPY
I think Andrew identified the critical point upthread: they don't try
to put an unlimited number of rows into
Marc G. Fournier wrote:
'k, so is the concensus here that I regenerate everything with the 'broken
msg seperator', and then revert to the unbroken one for new stuff? its no
sweat, I just fear this is going to re-crop up sometime in the future if
we ever have to regenerate from the mbox
Andreas,
Some weeks ago I proposed a PROGRESS parameter for COPY, to enable
progress feedback via notices. tgl thinks nobody needs that...
Well, *Tom* doesn't need it. What mechanism did you propose to make this
work?
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
75 matches
Mail list logo
