I don't rememeber we have submitted this module :-)
Doh - sorry!!!
I just extracted it from your tar.gz into my contrib - it's NOT in CVS!
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
-Forwarded Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Bug#139003: a little bit more is needed...
Date: 27 Mar 2002 00:21:18 -0800
reopen 139003
thanks
Looks like a small patch is needed as well to do the right thing on Linux.
The patch
On Wed, 27 Mar 2002, Tom Lane wrote:
Joel Burton [EMAIL PROTECTED] writes:
This will allow you to run a single postgres in a single jail only one
user would have access to it. If you try to run more then one it will
try to use the same shared memory and crash.
Is this, in fact, the
Christopher Kings-Lynne wrote:
I just sent in this email and it will appear immediately in the list.
Somewhat earlier, I have submitted a 25kb patch and then a 5kb gzipped
version of that patch to -hackers and -patches - it has not yet appeared on
the list.
What's going on? Do posts
Thanks. This is exactly the detail I needed. Let me comment on each
item.
Nicolas Bazin wrote:
Bruce,
The reason to move the socket library is that during configuration script
execution, the binary created core dumps if not in the order I gave. You can
check in the port list, some
- Original Message -
From: Bruce Momjian [EMAIL PROTECTED]
To: Nicolas Bazin [EMAIL PROTECTED]
Cc: PostgreSQL-development [EMAIL PROTECTED]
Sent: Wednesday, March 27, 2002 10:21 PM
Subject: Re: [HACKERS] build of 7.2.1 on SCO Openserver and Unixware 7.1.1
Thanks. This is exactly the
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
On Wed, 27 Mar 2002, Christopher Kings-Lynne wrote:
I just sent in this email and it will appear immediately in the list.
Somewhat earlier, I
On Tue, 26 Mar 2002, Stephan Szabo wrote:
On Tue, 26 Mar 2002, Jan Wieck wrote:
Tom Lane wrote:
I think the existing scheme of generating the plan during first use
in a particular backend is fine. At least as long as we're sticking
with standard plans at all ... IIRC Stephan was
Marc G. Fournier wrote:
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
OK, but should posters get email stating it is in the approval queue?
He clearly didn't, and I don't either, but
On Wed, 27 Mar 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
OK, but should posters get email stating it is in the approval queue?
Vince Vielhaber wrote:
On Wed, 27 Mar 2002, Bruce Momjian wrote:
Marc G. Fournier wrote:
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
OK, but should posters get email stating
Bruce Momjian [EMAIL PROTECTED] writes:
Yes, the patch replaces pow(8,*) with a lookup table of 4 8^X values.
So SCO provides a library you can't link to? Or you can't mix *.so
libraries and static *.a libraries? I am inclined ot add this patch to
the doc/FAQ_SCO file. We really try to
Peter Eisentraut wrote:
Tom Lane writes:
I don't think GRANT CONNECT fits into our setup at all. I also doubt
that it will be needed very much once we have schemas.
People have many times asked for a way to alter the connection settings
from within the database. For instance, you add
Alvaro Herrera writes:
I've been trying to generate HTML from the SGML source here in Mandrake
Linux 8.1, and it needs some patching (Mdk Linux puts collateindex.pl in
/usr/bin rather that $DOCBOOKSTYLE/bin).
I'll look at your patches soon. I've had some other ideas that I'd like
to weave
I have a postgresql DB that contains a lot of HTML code. As you know, HTML
contains numerous backslash( \ ) characters. When I use pg_dump to backup
the DB I get a CopyReadAttribute: end of record marker corrupted error. Is
there any way to circumvent this problem so that I can backup a DB
Peter Eisentraut [EMAIL PROTECTED] writes:
[ good stuff snipped ]
... Also, it prevents accidentally changing the locale when you
(or someone else) fiddle with your environment variables.
If I follow this correctly, the behavior would be that PG would not pay
attention to *any* LC_xxx
I see in quote.c::do_quote_ident():
*cp2++ = '';
while (len-- 0)
{
if (*cp1 == '')
*cp2++ = '';
if (*cp1 == '\\')
*cp2++ = '\\';
*cp2++ = *cp1++;
}
*cp2++ =
Bruce Momjian wrote:
I see in quote.c::do_quote_ident():
*cp2++ = '';
while (len-- 0)
{
if (*cp1 == '')
*cp2++ = '';
if (*cp1 == '\\')
*cp2++ = '\\';
*cp2++ = *cp1++;
}
*cp2++ = '';
I am confused by the backslash
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
To: Bruce Momjian [EMAIL PROTECTED]
Cc: Nicolas Bazin [EMAIL PROTECTED]; PostgreSQL-development
[EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 2:30 AM
Subject: Re: [HACKERS] build of 7.2.1 on SCO Openserver and Unixware 7.1.1
Here is the description:
When a macro is replaced by the preprocessor, pgc.l
reaches a end of file, which is not the actual end of the file. One side effect
of that is that if you are in a ifdef block, you get a wrong error telling you
that a endif is missing.
This patch corrects pgc.l and
On Wed, 2002-03-27 at 11:06, Peter Eisentraut wrote:
If someone is really bored out of their mind, at least one of these
warnings can be gotten rid of by not using the -l option to flex. That
might be desirable for other reasons, too, one of which is improved speed.
No, just removing -l
Neil Conway writes:
I'm curious; why is this not the right fix? According to the manpage:
-lturns on maximum compatibility with the original
ATT lex implementation. Note that this does not
mean full compatibility. Use of this option
costs a considerable amount
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
OH MY GOD!!!
I've always has this suspicion that every time I send an email with 'SET
NULL' in the subject it doesn't get through!!! I've even
Christopher Kings-Lynne wrote:
checking the moderator-to-approve listing for you, here are the reason(s):
Reason: GLOBAL ADMIN HEADER: /^subject:\s*set\b/i matched Subject: SET
OH MY GOD!!!
I've always has this suspicion that every time I send an email with 'SET
NULL' in the subject
Bruce Momjian [EMAIL PROTECTED] writes:
Christopher Kings-Lynne wrote:
I've always has this suspicion that every time I send an email with 'SET
NULL' in the subject it doesn't get through!!! I've even commented on that
on the list before!
The fact this is done silently is clearly
The fact this is done silently is clearly unacceptable.
Agreed. Curiously, though, I've always gotten notifications whenever
any of my messages got held up for moderator approval. Seems like there
are two questions for Marc here:
1. Why is the system failing to notify some people
Jan wrote:
There is a way to return anything. The problem in PostgreSQL
is to actually USE it.
Our idea originally was to extend the capabilities of a
rangetable entry. Currently, rangetable entries can only
hold a relation, which is a table or a view. After
27 matches
Mail list logo
