When compiled with gcc, it does trap divide by zero.
Alex
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
alex avriette <[EMAIL PROTECTED]> writes:
> I've got a 6-way SGI Challenge L with R4400/200 cpu's in it, and a gig
> of interleaved ram. I am running postgres 7.3.1, which I compiled
> 64-bit with MIPSPro.
> I'm finding that the Sparc 20 is about twice as fast as the Challenge.
I'm betting tha
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Sun, 2 Feb 2003, Neil Conway wrote:
>> - ensuring that end users can trust PostgreSQL is an important part to
>> getting the product used in mission-critical applications, as I'm sure
>> you all know. Part of that is producing good software; anoth
I have tried, without any luck, to get postgres compiled with gcc 3.2
(from freeware.sgi.com). It keeps adding '-r' when its linking, even
when LDFLAGS is unset, LD is 'gcc' and CC is 'gcc'. I could do the
linking manually, but this is not really a viable option for a >
release.
Looking at thi
I've got a 6-way SGI Challenge L with R4400/200 cpu's in it, and a gig
of interleaved ram. I am running postgres 7.3.1, which I compiled
64-bit with MIPSPro. The database is living on an ultrawide scsi raid.
I am also running postgres on a 2-cpu (85mhz) Sparc 20 with 384mb of
ram, and the datab
I found an example of a casting problem in our source code now that we're
running 7.3:
SELECT CURRENT_DATE - EXTRACT(DOW FROM CURRENT_DATE);
(Get's the start of the week);
This worked in 7.2, but fails in 7.3 with:
ERROR: Unable to identify an operator '-' for types 'date' and 'double
precision
Tom Lane wrote:
The plan for 7.3.2 release is for Marc to wrap the tarball tomorrow and
announce on Tuesday. I have already stamped the version number and
updated the release history in CVS, but is there anyone out there with
last-minute fixes?
In particular, is there anything that needs to be d
On Sunday 02 February 2003 21:23, Marc G. Fournier wrote:
> On Sun, 2 Feb 2003, Neil Conway wrote:
> > I think we should PGP sign all the "official" packages that are provided
> > for download from the various mirror sites. IMHO, this is important
> > because:
> right, that is why we started to pr
On Sun, 2 Feb 2003, Neil Conway wrote:
> Folks,
>
> I think we should PGP sign all the "official" packages that are provided
> for download from the various mirror sites. IMHO, this is important
> because:
>
> - ensuring that end users can trust PostgreSQL is an important part to
> getting the pro
On Sun, 2 Feb 2003, Bruce Momjian wrote:
> Yes, some have asked about this. My understanding was that CIDR
> (host/len) was mostly for networks, while hostname/mask was for hosts.
> Now, you can specify hosts using /32, but is is unusual? Maybe not.
Typically, if you have something like an acce
I don't think I was clear before. When someone is looking at the
interactive docs, I would like them to say, "Oh, there's a comment. I
better read that in case it will help me." If we have old comments,
their "special" value becomes diminished. That's why I think they
should be removed as they
Dave Page wrote:
> My concern here is that what (for example) Bruce decides is not a useful
> addition to the docs themselves, maybe something that would have helped
> me with some bizarre problem. If we dump *all* the docs after they have
> been merged then I might lose that helpful tip.
>
> Also
On Sun, 2003-02-02 at 18:39, Neil Conway wrote:
> Folks,
>
> I think we should PGP sign all the "official" packages that are provided
> for download from the various mirror sites. IMHO, this is important
> because:
>
> - ensuring that end users can trust PostgreSQL is an important part to
> getti
Folks, we want organized documentation, not cudos to commentors or
something that is so large that people have to wade through the comments
to see if something is interesting. The focus is the docs, and the
comments are only there to improve the docs. They are there for no
other reason.
---
Yes, please delete the old comments. We want to merge as many in as we
can, and remove the rest.
---
Dave Page wrote:
>
> As you may have noticed we have recently revamped the Interactive
> Documentation on the website (ht
Neil Conway <[EMAIL PROTECTED]> writes:
> I think we should PGP sign all the "official" packages that are provided
> for download from the various mirror sites.
This is probably a good idea.
> I'd volunteer to do the work myself, except that it's pretty closely
> intertwined with the release proc
Kurt Roeckx wrote:
> Currently in pg_hba.conf you specify the ip addresses that can
> connect with 2 fields: the ip address and the mask.
>
> What do you think about changing it to ip address/mask? Where
> mask can be both the current mask, or the prefix length.
>
> It's so much handier to use,
Folks,
I think we should PGP sign all the "official" packages that are provided
for download from the various mirror sites. IMHO, this is important
because:
- ensuring that end users can trust PostgreSQL is an important part to
getting the product used in mission-critical applications, as I'm sur
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Gavin Sherry wrote:
> >> I don't think we should listen on IPv6 just because it is supported. It
> >> should be a configuration variable:
> >>
> >> tcpip_socket = true
> >> ipv6 = true
>
> > We had a huge discussion on this. I think
> While we're talking about modifications to idocs, why not have a rating
> system for the usefulness of a comment.
Comment ratings could be useful if the rating is tied to a doc version.
A very useful 7.1 comment may be a little antiquated for 7.3. This
would solve almost all of the issues if c
Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > For example, the following query is not possible to
> > "workaround" in PostgreSQL:
>
> > select teams_desc.team_id, team_name, team_code, notes,
> > min(teams_tree.treeno) as lnode, max(teams_tree.treeno) as rnode,
> > parent.team_id
On 2 Feb 2003, Neil Conway wrote:
> On Sun, 2003-02-02 at 15:22, Dave Page wrote:
> > - Each comment attaches only to the page name, version of the page to
> > which it was submitted *and* subsequent versions (this is the current
> > behaviour).
> >
> > - Each comment should attach to the page
Curt Sampson <[EMAIL PROTECTED]> wrote:
> On Sun, 2 Feb 2003, Tom Lane wrote:
>
> > This all doesn't look good for using file locks in the way I had in
> > mind :-( ... but considering that all these man pages seem pretty vague,
> > maybe some direct experimentation is called for.
>
> Definitel
Hi,
I use it and can recommend it. It is actively developed/maintained (the
updates are free). There is very basic support of 7.3 schemas in the
new version for instance... And the development team is very responsive,
if you don't like or missing something write them...
kuba
On Sun, 2 Feb 2003 [
> -Original Message-
> From: Neil Conway [mailto:[EMAIL PROTECTED]]
> Sent: 02 February 2003 20:52
> To: Dave Page
> Cc: PostgreSQL Hackers
> Subject: Re: [HACKERS] Interactive Documentation - how do you
> want it towork?
>
> > 2) Bearing in mind your answer to the previous question, sh
Tom,
> I think you are leaping to conclusions about why there's a speed
> difference. Or maybe I'm too dumb to see how an index could be used
> to speed these min/max operations --- but I don't see that one would
> be useful. Certainly not an index on treeno alone. Would you care to
> explain e
On Sun, 2003-02-02 at 15:22, Dave Page wrote:
> - Each comment attaches only to the page name, version of the page to
> which it was submitted *and* subsequent versions (this is the current
> behaviour).
>
> - Each comment should attach to the page name to which it was submitted
> regardless of
Neil Conway <[EMAIL PROTECTED]> writes:
> On Sun, 2003-02-02 at 15:15, Tom Lane wrote:
>> I was thinking of that as a feature addition, but you still have time
>> to convince me it's a bug fix ...
> IMHO, it's a bugfix, or at least fixes a notable omission: the
> documented function of PQcmdTuples
Josh Berkus <[EMAIL PROTECTED]> writes:
> For example, the following query is not possible to
> "workaround" in PostgreSQL:
> select teams_desc.team_id, team_name, team_code, notes,
> min(teams_tree.treeno) as lnode, max(teams_tree.treeno) as rnode,
> parent.team_id as parent_id, count(*)/2 as tl
On Sun, 2003-02-02 at 13:04, Tom Lane wrote:
> I think your test case is small enough that the whole table is resident
> in memory, so this measurement only accounts for CPU time per tuple and
> not any I/O. Given the small size of pgstattuple's per-tuple loop, the
> speed differential is not too
On Sun, 2003-02-02 at 15:15, Tom Lane wrote:
> I was thinking of that as a feature addition, but you still have time
> to convince me it's a bug fix ...
IMHO, it's a bugfix, or at least fixes a notable omission: the
documented function of PQcmdTuples is that it "Returns the number of
rows affected
Tom,
> In the end, the only reasonable way to handle this kind of thing is
> to teach the query planner about it. Considering the small number
> of cases that are usefully optimizable (basically only MIN and MAX
> on a single table without any WHERE or GROUP clauses), and the ready
> availability
As you may have noticed we have recently revamped the Interactive
Documentation on the website (http://www.postgresql.org/docs). This has
raised a couple of questions about how the idocs should work, so I'd
like to get some votes on the following 2 issues:
1) How should comments be linked to docu
Neil Conway <[EMAIL PROTECTED]> writes:
> I posted a patch fixing PQcmdTuples() for some additional commands --
> should that go into 7.3.2?
I was thinking of that as a feature addition, but you still have time
to convince me it's a bug fix ...
regards, tom lane
-
On Sun, 2003-02-02 at 14:59, Tom Lane wrote:
> The plan for 7.3.2 release is for Marc to wrap the tarball tomorrow and
> announce on Tuesday. I have already stamped the version number and
> updated the release history in CVS, but is there anyone out there with
> last-minute fixes?
I posted a patc
The plan for 7.3.2 release is for Marc to wrap the tarball tomorrow and
announce on Tuesday. I have already stamped the version number and
updated the release history in CVS, but is there anyone out there with
last-minute fixes?
In particular, is there anything that needs to be done to update the
> -Original Message-
> From: Justin Clift [mailto:[EMAIL PROTECTED]]
> Sent: 02 February 2003 15:01
> To: Bruce Momjian
> Cc: Lamar Owen; PostgreSQL-development
> Subject: Re: [HACKERS] Windows Build System - My final thoughts
>
> >> Hey, if we make a really
> >>bad impression with th
Currently in pg_hba.conf you specify the ip addresses that can
connect with 2 fields: the ip address and the mask.
What do you think about changing it to ip address/mask? Where
mask can be both the current mask, or the prefix length.
It's so much handier to use, especially for ipv6.
Kurt
---
On Sun, 2 Feb 2003, Tom Lane wrote:
> This all doesn't look good for using file locks in the way I had in
> mind :-( ... but considering that all these man pages seem pretty vague,
> maybe some direct experimentation is called for.
Definitely. I wonder about the NetBSD manpage quotes in the post
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> [virtual_host] currently only seems to support 1 address, and I don't really
> know why. Is there a reason you can't make this a list of
> hostnames/ip addresses?
That was what the boys at uu.net needed, so that's what they
implemented. If you need more,
On Sunday 02 February 2003 12:26, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > Also odd, why would running over NFS have any bearing on it if we
> > could find such a place?
>
> Yup, 'tis the question. The only theory I have been able to come up
> with is that there's somet
On Sun, Feb 02, 2003 at 12:49:34PM -0500, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Gavin Sherry wrote:
> >> I don't think we should listen on IPv6 just because it is supported. It
> >> should be a configuration variable:
> >>
> >> tcpip_socket = true
> >> ipv6 = true
>
> >
On Sun, 2 Feb 2003, Tom Lane wrote:
> I think I was the one who talked us into assuming that ipv4 and ipv6
> should be treated as a single protocol. But some people have since made
> pretty good cases that it's better to regard them as separate protocols.
>From a security standpoint, I think it'
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> In special cases there can be another way to avoid seq scans:
> [ use pgstattuple() ]
But pgstattuple does do a sequential scan of the table. You avoid a lot
of the executor's tuple-pushing and plan-node-traversing machinery t
Neil Conway wrote:
On Sun, 2003-02-02 at 03:55, Hans-Jürgen Schönig wrote:
If people want to count ALL rows of a table. The contrib stuff is pretty
useful. It seems to be transaction safe.
Interesting -- I didn't know about the contrib stuff. I'll update the
docs patch.
Cheers,
Neil
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Gavin Sherry wrote:
>> I don't think we should listen on IPv6 just because it is supported. It
>> should be a configuration variable:
>>
>> tcpip_socket = true
>> ipv6 = true
> We had a huge discussion on this. I think you were away for it. You
> can
On Sun, 2 Feb 2003, Kurt Roeckx wrote:
> On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
> >
> > Sure. But you still want to be able to say (and can say, in some [many?]
> > socket API implementations) that you want to accept only IPv4 or only IPv6
> > connections. I also want to be
Has anyone seriously tried out this package?
It looks like a "cheaper variant on ERWin," with the merit of having
some PostgreSQL support.
It only runs on WinTel, which is somewhat unfortunate, but I haven't
gotten the sort of diagramming I have been looking for out of AutoDoc,
so I'd be game t
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> Also odd, why would running over NFS have any bearing on it if we
> could find such a place?
Yup, 'tis the question. The only theory I have been able to come up
with is that there's something flaky about your network hardware,
such that Postgres s
On Sun, 2003-02-02 at 03:55, Hans-Jürgen Schönig wrote:
> If people want to count ALL rows of a table. The contrib stuff is pretty
> useful. It seems to be transaction safe.
Interesting -- I didn't know about the contrib stuff. I'll update the
docs patch.
Cheers,
Neil
--
Neil Conway <[EMAIL P
From: "Bruce Momjian" <[EMAIL PROTECTED]>
>
> I am using SRA's Win32 port here on XP, and it doesn't use readline.
>
> It does have arrow handling for psql, but does not do Control-A/E
> handling, nor keep the history between psql invocations. I assume this
> is what the limited command-line hand
Bruce Momjian wrote:
Justin Clift wrote:
+ Aside from all this, it might be nice to have a few Win32 specific
gui pieces in place at the time that PostgreSQL 7.4 Win32 is released.
Am sure they'll develop over time, but was thinking we should at least
make a good impression with the first re
Gavin Sherry wrote:
> On Sun, 2 Feb 2003, Bruce Momjian wrote:
>
> > Kurt Roeckx wrote:
> > > On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
> > > >
> > > > Sure. But you still want to be able to say (and can say, in some [many?]
> > > > socket API implementations) that you want to
On Sun, 2 Feb 2003, Bruce Momjian wrote:
> Kurt Roeckx wrote:
> > On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
> > >
> > > Sure. But you still want to be able to say (and can say, in some [many?]
> > > socket API implementations) that you want to accept only IPv4 or only IPv6
> >
On Saturday 01 February 2003 15:48, Tom Lane wrote:
> More and more bizarre. What is the hardware platform --- does it have TAS?
NetBSD on a Pentium (i386 port) so yes, it does have TAS. I assume you were
thinking about the spinlock emulation.
I have been looking through backend/storage/lmgr/l
On Sun, Feb 02, 2003 at 08:19:23AM -0500, Bruce Momjian wrote:
> Kurt Roeckx wrote:
> > Depending on the OS, binding to all addresses on IPv6 will also
> > bind to all the ipv4 addresses, which can be both handy an
> > annoying. On others you need 2 sockets if you want to listen on
> > both ipv4 a
Kurt Roeckx wrote:
> On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
> >
> > Sure. But you still want to be able to say (and can say, in some [many?]
> > socket API implementations) that you want to accept only IPv4 or only IPv6
> > connections. I also want to be able to say the same
On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
>
> Sure. But you still want to be able to say (and can say, in some [many?]
> socket API implementations) that you want to accept only IPv4 or only IPv6
> connections. I also want to be able to say the same thing in my database.
You j
You can't because the backend opens that file as the super-user. You
can use \copy in psql as an normal user, though.
---
Jaume Teixi wrote:
> how should I use " COPY arti FROM 'ARTI.txt' USING DELIMITERS '|' " as normal u
Justin Clift wrote:
> + Aside from all this, it might be nice to have a few Win32 specific
> gui pieces in place at the time that PostgreSQL 7.4 Win32 is released.
> Am sure they'll develop over time, but was thinking we should at least
> make a good impression with the first release. Hey, if
Jeff Davis wrote:
> > As for build environment, we have two audiences --- those using
> > binaries, and those compiling from source. Clearly we are going to have
> > more binary users vs. source users on Win32 than on any other platform,
> > so at this stage I think making thing easier for the maj
Lamar Owen wrote:
> On Friday 31 January 2003 03:21, Bruce Momjian wrote:
> > Man, I go away for one day, and look what you guys get into. :-)
>
> No duh. Whew.
>
> > Lastly, SRA just released _today_ their first Win32 port of PostgreSQL,
> > and it is _threaded_:
>
> > http://osb.sra.co.j
Andrew Dunstan wrote:
> I think I have sorted through the confusion.
>
> Looks like the only thing cygwin might be used for is a client. Here's what
> the manual that comes with the 4.0.9gamma source says:
>
> There are two versions of the MySQL command-line tool: Binary Description
> mysq
This patch adds a note to the documentation describing why the
performance of min() and max() is slow when applied to the entire table,
and suggesting the simple workaround most experienced Pg users
eventually learn about (SELECT xyz ... ORDER BY xyz LIMIT 1).
Any suggestions on improving the word
Giles Lean <[EMAIL PROTECTED]> writes:
> Boring reference material follows.
Couldn't help noticing that you omitted HPUX ;-)
On HPUX 10.20, flock doesn't seem to exist (hasn't got a man page nor
any mention in /usr/include). lockf says
All locks for a process are released upon
the fir
65 matches
Mail list logo
