Re: [HACKERS] Hacking PostgreSQL to work in Mac OS X 10.3 (Panther 7B85)

2003-10-12 Thread Marko Karppinen
On 12.10.2003, at 03:52, James Wilson wrote: I've done a checkout from CVS and performed a build under OS X Panther 7B85 with the non-hacked header files. The problem with the param.h header file seems to be fixed, however the build is failing with undefined symbols in libs: I believe you have s

[HACKERS] question about CURSOR

2003-10-12 Thread ivan
Hi, How can i check how many tules has my declared cursor ? I can set absolute position in cursor , but i dont know how far can i go ? I need it also to set size of my scroll . One more question , when i use declare cursor to show select on grid, better is to use cursor in BEGIN/END WORK, or WITH

[HACKERS] Question on "current_user"

2003-10-12 Thread Michael Brusser
Is there something special about function current_user? In v.7.3.4 it only works when I do "select current_user;" and breaks when called with the empty arg. list: syncdb=# select current_user(); ERROR: parser: parse error at or near "(" at character 20 This behavior is just the opposite to t

Re: [HACKERS] rt_sigprocmask

2003-10-12 Thread Gaetano Mendola
Gaetano Mendola wrote: Hi all, I'm importing on Postgres 7.3.4 a dump and after one hour the process is still there to perform a COPY of a table with about ~1.5M rows. BTW after 2 days the process is still importing :-( Gaetano ---(end of broadcast)

Re: [HACKERS] Question on "current_user"

2003-10-12 Thread Peter Eisentraut
Michael Brusser writes: > Is there something special about function current_user? Yes. > In v.7.3.4 it only works when I do "select current_user;" > and breaks when called with the empty arg. list: That is the special thing. It's bizarre, but that's how SQL wants it. I've wanted to extend it s

[HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Peter Eisentraut
I've always been uneasy about the notice at the end of the installation process that asks the user to register at http://www.pgsql.com/register/submit.php Now some users have also complained to me about that, so I'm wondering what others think about it. First, I think collecting addresses from u

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Dave Page
> -Original Message- > From: Peter Eisentraut [mailto:[EMAIL PROTECTED] > Sent: 12 October 2003 14:02 > To: PostgreSQL Development > Subject: [HACKERS] http://www.pgsql.com/register/submit.php > > I've always been uneasy about the notice at the end of the > installation process that a

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Michael Meskes
On Sun, Oct 12, 2003 at 03:01:39PM +0200, Peter Eisentraut wrote: > First, I think collecting addresses from users is something that an > open-source project should never do. It's what makes them stand out from > packages with annoying license requirements. Couldn't agree more. > Third, the meth

[HACKERS] Still not able to initdb

2003-10-12 Thread Michael Meskes
Hi, I just tried the latest Debian packages for beta4 and I still cannot initdb. It's the same old problem. Once I add a "\." to sql_features.txt it works well, but without it it errors out. Needless to say that the 'echo "\."' is there in initdb, but it still doesn't work without the additional

Re: [HACKERS] VARHDRSZ

2003-10-12 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > For formatting types pre-7.1, how do I know what the value of VARHDRSZ > is? (Given that it's a PHP script, say.) It's 4. regards, tom lane ---(end of broadcast)--- TIP

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > I've always been uneasy about the notice at the end of the installation > process that asks the user to register at > http://www.pgsql.com/register/submit.php There was discussion of rewording that message some time ago, but nothing happened. (I thin

Re: [pgsql-hackers-win32] [HACKERS] initdb

2003-10-12 Thread Andrew Dunstan
Bruce, I think this is now ready to import into the WIN32 branch. I have ironed out the cygwin dependencies, and posted a note about what we'll need to do inside postgres to handle the environment values for setlocale() on Windows. If you want to rip out the unlink stuff (see previous email thre

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Marc G. Fournier
On Sun, 12 Oct 2003, Peter Eisentraut wrote: > Fourth, the registration is run not by the project but by a commercial > company. That seems inappropriate for all the reasons you can imagine. To be honest, I don't know why it was every put on pgsq.com in the first place, and think the whole thin

[HACKERS] NOTICE: Servers down on Monday, Oct 13th

2003-10-12 Thread Marc G. Fournier
Just a quick note to everyone that the servers will be down for serveral hours on Monday in order to move them. We've been told to expect ~6hrs of downtime to do it, but since its just moving down the street, we hope it to be less then that. At the new location, our IPs are changing to our own I

Re: [HACKERS] more i18n/l10n issues

2003-10-12 Thread Peter Eisentraut
Tom Lane writes: > -m and -M > > The utility we designed and possibly any other that wants to process the > output will find it easier to process a more regularly formed output > instead of one that was embellished for human viewing. The reason for > having one with and one without headings is th

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Peter Eisentraut
Tom Lane writes: > I agree that there's no need to ask people to register. I think it'd > be okay to have a message that suggests visiting www.postgresql.org. The text already suggests www.postgresql.org, so there's nothing to do besides removing the register bit, if we agree to do so. However,

[HACKERS] Heading to final release

2003-10-12 Thread Bruce Momjian
We only have a few open items left. Let's make final decisions on these and schedule RC1. --- P O S T G R E S Q L 7 . 4 O P E NI T E M S Current at ftp://momj

[HACKERS]

2003-10-12 Thread sabrina lal
Hello I am new to development on postgreSQL. I and my collegues are working on mechanisms for query rewriting, containment and view set selections and we have chosen postgreSQL to work with. I found out that the debug levels and EXPLAIN command lets you know the selection made at each step of

Re: [HACKERS] Heading to final release

2003-10-12 Thread Christopher Kings-Lynne
Changes --- Allow superuser (dba?) the ability to turn off foreign key checks/all constraints/triggers, not settable from postgresql.conf? Is that one really necessary for 7.4 now that adding foreign keys is apparently much faster? Chris ---(end of broadcast)

Re: [HACKERS] Heading to final release

2003-10-12 Thread Bruce Momjian
Christopher Kings-Lynne wrote: > > > Changes > > --- > > Allow superuser (dba?) the ability to turn off foreign key checks/all > > constraints/triggers, not settable from postgresql.conf? > > Is that one really necessary for 7.4 now that adding foreign keys is > apparently much faster? Th

Re: [HACKERS] http://www.pgsql.com/register/submit.php

2003-10-12 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > However, I think the message is a bit pointless altogether. You have a point. Anyone against ripping it out entirely? If so, what needs to be said in this message? regards, tom lane ---(end of broadc

Re: [HACKERS]

2003-10-12 Thread Tom Lane
"sabrina lal" <[EMAIL PROTECTED]> writes: > I found out that the debug levels and EXPLAIN command lets you know the > selection made at each step of the query execution. I wanted to know if > there was or there can be a way to find out what query paths are considered > while forming the query ex

Re: [HACKERS] Still not able to initdb

2003-10-12 Thread Michael Meskes
On Mon, Oct 13, 2003 at 02:38:26AM +0100, Oliver Elphick wrote: > On Sun, 2003-10-12 at 13:27, Michael Meskes wrote: > > I just tried the latest Debian packages for beta4 and I still cannot > > initdb. It's the same old problem. Once I add a "\." to sql_features.txt > > it works well, but without i