I wrote this patch for my system, and it works fine. However, it's a really ugly
workaround. I can publish the source
if anybody is interested.
Am Montag, 26. August 2002 06:33 schrieb Thomas O'Dowd:
> Thanks for your feedback Stephan. Seems like a tough fix. Pitty it won't
> make it into 7.3. I
> the release docs are pulled from petere's account:
>
> cp ~petere/man.tar.gz ~petere/postgres.tar.gz doc
They are too old.
$ ls -l man.tar.gz postgres.tar.gz
-rw-r--r-- 1 petere wheel 125177 Mar 27 11:51 man.tar.gz
-rw-r--r-- 1 petere wheel 843714 Mar 26 23:39 postgres.tar.gz
--
Tatsuo
*sigh* Someone's marked postgres 7.2.1 as forbidden in FreeBSD ports:
FORBIDDEN= "buffer overruns acknowledged by authors--see
http://www3.us.postgresql.org/news.html>"
Somewhat of an overreaction...I'm hassling the maintainer at the moment...
Chris
> -Original Message-
> From: [E
On 26 Aug 2002, Thomas O'Dowd wrote:
> Thanks for your feedback Stephan. Seems like a tough fix. Pitty it won't
> make it into 7.3. I presume there are other folk out there suffering
> from the same problems that I'm having. What approaches if any have
> people taken to work around this problem?
Thanks for your feedback Stephan. Seems like a tough fix. Pitty it won't
make it into 7.3. I presume there are other folk out there suffering
from the same problems that I'm having. What approaches if any have
people taken to work around this problem? I read in the list that one
user patched his p
the release docs are pulled from petere's account:
cp ~petere/man.tar.gz ~petere/postgres.tar.gz doc
On Mon, 26 Aug 2002, Christopher Kings-Lynne wrote:
> I say a re-release of 7.2.2 is sufficient, as it's just docs...
>
> What docs were in there? 7.3? or 7.2.1?
>
> Chris
>
> > -Origina
On Sun, 25 Aug 2002, Bruce Momjian wrote:
> Do we want to add "query caching" to the TODO list, perhaps with a
> question mark?
I'd love to have query plans cached, preferably across backends.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you kno
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> + if (!superuser() && MyBackendId > MaxBackends - ReservedBackends)
> + elog(ERROR, "Normal user limit exceeded");
This coding is wrong on its face: the slot number you happen to find has
no relationship to the number of slots remai
I say a re-release of 7.2.2 is sufficient, as it's just docs...
What docs were in there? 7.3? or 7.2.1?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tatsuo Ishii
> Sent: Monday, 26 August 2002 11:59 AM
> To: [EMAIL PROTECTED]
> Subject:
> Does anybody know 7.2.2 if xtar ball has been repacked? Peter pointed
> out the previous tar ball included wrong docs.
I have confirmed
cvs.postgres.org://var/spool/ftp/pub/source/v7.2.2/postgresql-7.2.2.tar.gz
(-rw-r--r-- 1 pgsql pgsql 9239158 Aug 22 23:25 postgresql-7.2.2.tar.gz)
includ
On 26 Aug 2002, Thomas O'Dowd wrote:
> Hi all,
>
> I've been having a lot of trouble with deadlocks in 7.2.1 because of
> foreign keys. I dug out a couple of messages from the list archives
> which cover this topic.
>
> One particular message indicates a fix was being worked on.
>
> Dat
Hi all,
I've been having a lot of trouble with deadlocks in 7.2.1 because of
foreign keys. I dug out a couple of messages from the list archives
which cover this topic.
One particular message indicates a fix was being worked on.
Date: Thu, 11 Apr 2002 09:03:06 -0700 (PDT)
From: Stephan
On Sun, 25 Aug 2002, Bruce Momjian wrote:
>
> OK, I understand your point. What do we need to do now that the
> announcement has already been made?
I'm still slightly confused here ... from what Neil/Gavin have stated so
far, all it sounds like is that if I pass a wrong date/time string, it
wil
Does anybody know 7.2.2 if xtar ball has been repacked? Peter pointed
out the previous tar ball included wrong docs.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
I'm not sure about query result caching or 'relation caching', since the
first would seem to run into problems with concurrent updates, and the
second is sort-of what the buffer cache does.
Query plan caching sounds like a really good idea though. Neil Conway's
PREPARE patch already does this for
Do we want to add "query caching" to the TODO list, perhaps with a
question mark?
---
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSA
TODO item:
Administration -
Reserve last few process slots for super-user if max_connections
reached
Notes:
Added GUC superuser_reserved_connections such that non-superuser connections
are only acceptable in the first
(max_connections - superuser_reserved_connections) backend
I have been corresponding with Bob Devine for a few years. He was at
Berkeley during the Postgres days and knows quite a bit about
optimizers and storage systems. I will put his name at the bottom of
the optimizer README and if people have questions, he is willing to
answer them as best he can.
I am going through my mailbox trying to tie up any loose ends before
beta. This is SOP --- standard operating procedure. ;-)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Rob
Should this capability be added some day?
---
Fernando Nasser wrote:
>
> Tom Lane wrote:
> >
> > Fernando Nasser <[EMAIL PROTECTED]> writes:
> > > This is a patch that was posted some time ago to pgsql-patches and
> > > n
Igor, we have split out the System V shared memory and IPC stuff into
separate files in the current CVS. Would you be able to make POSIX
files that would work on QNX6? It is on our TODO list to get QNX6
working for 7.3, and you are the most capable person to do this.
(FYI, I have heard reports
Jeffrey, I have several Perl:DBD patches my mailbox that I have
accumulated over the years that never made it over to Edmund or
yourself. Would you like them?
Also, would you consider creating a Pg:DBD project on
http://gborg.postgresql.org. We are trying to get all the PostgreSQL
interfaces
Created on gborg as pgperl.
---
Marc G. Fournier wrote:
> On 22 Aug 2002, Neil Conway wrote:
>
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > Just got a note from Jeffrey on this, and he acknowledges that he is
>
Gavin Sherry <[EMAIL PROTECTED]> writes:
> So, the question is this: should there be documentation of the maximum
> string length of a data structure so that application programmers can
> provide string length validation?
I don't think so; that's just going to make it harder to fix things if,
say
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> It is a GUC. It's exactly like max_backends. I took the easy route out and
> just followed where DEF_MAXBACKENDS was being set rather than hard wiring
> the value any where.
Oh. Well, skip the configure part: the only reason there's still a
config
On Sun, 25 Aug 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > + AC_MSG_CHECKING([for default superuser reserved number of connections])
> > + PGAC_ARG_REQ(with, reservedbackends, [ --with-reservedbackends=Nset default
>superuser reserved number of connections [2]
;;; From: [EMAIL PROTECTED]
;;; Date: Tue, 16 Jul 2002 10:22:14 +0900 (JST)
;;;
;;; ;;; However, that doesn't explain our OS
Hi all,
I've just been thinking that the documentation doesn't cover the maximum
input string lengths for various data types well. Case in point, the
date/time code: there was a fair amount of discussion about validation
input, including checking for 'unreasonable' string lengths. Unless you
went
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> + AC_MSG_CHECKING([for default superuser reserved number of connections])
> + PGAC_ARG_REQ(with, reservedbackends, [ --with-reservedbackends=Nset default
>superuser reserved number of connections [2]],
> + [],
> + [wi
No, they aren't.
You should call textout if you want to convert a TEXT object into a C
string.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
OK, I understand your point. What do we need to do now that the
announcement has already been made?
---
Gavin Sherry wrote:
> On Sat, 24 Aug 2002, Bruce Momjian wrote:
>
> >
> > The issue is data-provoked crashes vs. que
On Sat, 24 Aug 2002, Bruce Momjian wrote:
>
> The issue is data-provoked crashes vs. query-invoked crashes. Marc's
> point, and I think it was clear enough, is that you can't just poke at
> the TCP port and hope to do anything bad, which was the thrust of the
> argument, I think.
Bruce,
I am
Helps if I attach the patch...
-- Forwarded message --
Date: Sun, 25 Aug 2002 14:36:19 +0100 (BST)
From: Nigel J. Andrews <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: A configure.in patch check
Would someone apply the attached patch to the development source and let me
Would someone apply the attached patch to the development source and let me
know if the autoconf step fails or works. I've only got autoconf 2.13 available
and the file needs 2.53 apparently. If it works could I also have a copy of the
resulting configure script, or patch, please.
For the recor
34 matches
Mail list logo
