Am Donnerstag, 18. November 2004 22:07 schrieb Josh Berkus:
a) new users try just to psql as postgres, and get a no such database
postgres;
This problem has been recognized before. I think a possible solution is to
make psql recognize the error (the error code regime in libpq would have to
Hello,
I'm working on a thesis project where I explore the addition of a
specialized, bioinformatics-related data type to a RDBMS. My choice of
RDBMS is PostgreSQL, of course, and I've started by adding a dnaseq (DNA
sequence) data type, using PostgreSQL's APIs for type additions.
The idea is to
Tom Lane said:
Josh Berkus [EMAIL PROTECTED] writes:
I would agree that seems a little odd ;). Would this be something we
want done for 8.0?
I think we'd better. Otherwise, people will get used to the broken
syntax.
Agreed. Someone's going to step up and patch this, no?
(Not me ---
Hi,
your project looks very attractive. In principle, suffix array should be
implemented using GiST framework. String Btree should be very useful
for your problem. My student is working on string btree library, but we
have no plan to intergrate it into postgresql.
Oleg
On Fri, 19 Nov 2004,
On R, 2004-11-19 at 12:42, Troels Arvin wrote:
The basic parts of the type are pretty much done. Those interested may
have a look at http://troels.arvin.dk/svn-snap/postgresql-dnaseq/ (the
code organization needs some clean-up). The basic type implementation
should be improved by adding more
Hi Troels,
This is not related to the database aspects of your question... But there
are more than 4 possible letters in DNA sequences, 16 in fact. Depending on
the accuracy of the DNA sequences you are storing, you may come across
ambiguity DNA bases, so your type will have to take these into
Hello Oleg,
On Fri, 2004-11-19 at 15:35 +0300, Oleg Bartunov wrote:
your project looks very attractive.
Thanks.
In principle, suffix array should be implemented using GiST framework.
But in a previous conversation between the two of us, you wrote that the
GiST wasn't suitable for this
On Fri, 19 Nov 2004 14:38:20 +0200, Hannu Krosing wrote:
Part of my current code concerns packing DNA characters: As the alphabet
of DNA strings is very small (four characters), it seems like a
straigt-forward optimization to store each character in two bits.
My advice would be to get it
I am running of postgresql database servers with generally 30-50 users
at a time per server. I have noticed one thing for web based databases
that they fail to initialse a pg_connection connection every now and
again and return no error message at all.
I am thinking of the PG_SOMAXCONN
On Fri, 19 Nov 2004, Troels Arvin wrote:
Hello Oleg,
On Fri, 2004-11-19 at 15:35 +0300, Oleg Bartunov wrote:
your project looks very attractive.
Thanks.
In principle, suffix array should be implemented using GiST framework.
But in a previous conversation between the two of us, you wrote that the
Humor the Canadian ... when is Thanksgiving? :)
Next week.. :) Thursday.
Marc G. Fournier Hub.Org Networking Services
(http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ:
7615664
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Donnerstag, 18. November 2004 22:07 schrieb Josh Berkus:
a) new users try just to psql as postgres, and get a no such database
postgres;
This problem has been recognized before. I think a possible solution is to
make psql recognize the error
On Fri, 19 Nov 2004, Joshua D. Drake wrote:
Humor the Canadian ... when is Thanksgiving? :)
Next week.. :) Thursday.
Thank you ... I knew you guys celebrated later then us, just didn't know
why ... do you guys celebrate Remembrance Day same as us, or different
too? Ours is Nov 11 ...
I can't get too excited about this, to be honest. What I would like to
see, either in contrib or on pgfoundry, is one or more moderately
complete and well populated sample databases.
cheers
andrew
Josh Berkus wrote:
Folks,
Some issues have come up repeatedly on IRC with new users, enough so
Troels Arvin [EMAIL PROTECTED] writes:
2. Does someone know of interesting documentation (perhaps
in the form of interesting code comments) which I should
read, as a basis for creating a non-standard index type
in PostgreSQL?
There's not a whole lot :-( and you should definitely
Am Freitag, 19. November 2004 15:59 schrieb Tom Lane:
is to make psql recognize the error (the error code regime in libpq would
have to be extended for that),
Extended how? The error you're interested in will come back as
ERRCODE_UNDEFINED_DATABASE.
AFAICT, error codes are only accessible
On Fri, 2004-11-19 at 10:42, Troels Arvin wrote:
Hello,
I'm working on a thesis project where I explore the addition of a
specialized, bioinformatics-related data type to a RDBMS. My choice of
RDBMS is PostgreSQL, of course, and I've started by adding a dnaseq (DNA
sequence) data type,
Peter Eisentraut [EMAIL PROTECTED] writes:
AFAICT, error codes are only accessible through PGresult. But if the
connection attempt fails, you have at best a PGconn. This is the same kind
of issue we have with frontends parsing the no password supplied message,
because PQconnect cannot
Andrew Dunstan wrote:
I can't get too excited about this, to be honest. What I would like to
see, either in contrib or on pgfoundry, is one or more moderately
complete and well populated sample databases.
How about the tpcw database model, filled with some real world data
(e.g. pgsql books)?
Thank you ... I knew you guys celebrated later then us, just didn't know
why ... do you guys celebrate Remembrance Day same as us, or different
too? Ours is Nov 11 ...
I don't even know what Rememberance Day is ;)
Sincerely,
Joshua D. Drake
Marc G. Fournier Hub.Org Networking
Hi all,
I've cleaned this up a bit so that assigning to a dynamic record field
now works - ie NEW.(myvar) := 'someval' - and accessing a field by
number works - ie myvar := OLD.(1)
It still doesn't work in a loop if the type of field referenced by the
expression changes - looking at it more I'm
Joshua D. Drake [EMAIL PROTECTED] writes:
Thank you ... I knew you guys celebrated later then us, just didn't
know why ... do you guys celebrate Remembrance Day same as us, or
different too? Ours is Nov 11 ...
I don't even know what Rememberance Day is ;)
WWI ended on November 11, 1918.
Andrew,
I can't get too excited about this, to be honest. What I would like to
see, either in contrib or on pgfoundry, is one or more moderately
complete and well populated sample databases.
How about the tpcw database model, filled with some real world data
(e.g. pgsql books)? Other
Josh Berkus wrote:
Andrew,
I can't get too excited about this, to be honest. What I would like to
see, either in contrib or on pgfoundry, is one or more moderately
complete and well populated sample databases.
How about the tpcw database model, filled with some real world data
(e.g. pgsql books)?
On Fri, Nov 19, 2004 at 05:29:20AM -0600, Andrew Dunstan wrote:
Tom Lane said:
Josh Berkus [EMAIL PROTECTED] writes:
I would agree that seems a little odd ;). Would this be something we
want done for 8.0?
I think we'd better. Otherwise, people will get used to the broken
syntax.
Hmmm ... sounds like an add-in project.I'm not sure, I think something
which demonstrates more general principles than the TPC-W database would be
useful, sort of a training database.Maybe one of the writers of PGSQL
books has such a thing? Maybe Bruce?
I have the complete books
Joshua D. Drake wrote:
I have the complete books database that we used in Practical PostgreSQL.
I would want to do a little work on it to get it up to snuff (add
comments etc..) but it would be a start.
Is the DDL online somewhere to peek at it?
Regards,
Andreas
---(end
Tom Lane wrote:
The answer is: it's a gcc bug. The attached program should print
x = 12.3
y = 12.3
but if compiled with -O or -O2 on Stefan's machine, I get garbage:
$ gcc -O ftest.c
$ ./a.out
x = 12.3
y = 1.47203e-39
woa - scary. I will report that to the OpenBSD-folks upstream - many
thanks
plperl's error handling is not completely broken, but it's close :-(
Consider for example the following sequence on a machine with a
relatively old Perl installation:
regression=# create or replace function foo(int) returns int as $$
regression$# return $_[0] + 1 $$ language plperl;
CREATE
Stefan Kaltenbrunner wrote:
Tom Lane wrote:
The answer is: it's a gcc bug. The attached program should print
x = 12.3
y = 12.3
but if compiled with -O or -O2 on Stefan's machine, I get garbage:
$ gcc -O ftest.c
$ ./a.out
x = 12.3
y = 1.47203e-39
woa - scary. I will report that to the
David Fetter [EMAIL PROTECTED] writes:
So it's a case of bad documentation, which we will fix very shortly. Sorry
for the noise.
Please find attached a patch that fixes this.
Applied, thanks.
regards, tom lane
---(end of
Tom Lane wrote:
What I think we ought to do is change both PL languages so that every
SPI call is executed as a subtransaction. If the call elogs, we can
clean up by aborting the subtransaction, and then we can report the
error message as a Perl or Tcl error condition, which the function
author
Tom Lane wrote:
plperl's error handling is not completely broken, but it's close :-(
Consider for example the following sequence on a machine with a
relatively old Perl installation:
You just picked an easy way to trigger this. As you rightly observe,
there are others.
We can deal with this
Andrew Dunstan [EMAIL PROTECTED] writes:
Meanwhile, what do we do? Turn off -O in src/template/openbsd for
some/all releases?
Certainly not. This problem is only known to exist in one gcc version
for one architecture, and besides it's only affecting (so far as we can
tell) one rather
Thomas Hallgren [EMAIL PROTECTED] writes:
My approach with PL/Java is a bit different. While each SPI call is
using a try/catch they are not using a subtransaction. The catch will
however set a flag that will ensure two things:
1. No more calls can be made from PL/Java to the postgres
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
This will slow down the PL SPI call operations in both languages, but
AFAICS it's the only way to provide error handling semantics that aren't
too broken for words.
Can you estimate the extent of the slowdown?
Without actually doing
Kris,
Environment #1: WinXP 8.0beta4 server, 8.0jdbc client
I get random failures with the following errors:
$ grep ERROR postgresql-2004-11-19_091524.log
2004-11-19 12:19:06 ERROR: unrecognized node type: 25344832
2004-11-19 12:20:06 ERROR: unrecognized node type: 25344832
2004-11-19
37 matches
Mail list logo