said, I would have submitted a patch with said
> documentation if I knew where to start. I have submitted this RFC -- a
> request for comments, nothing more serious than that -- because I'd
> like to know what we can do to get some documentation included in the
> next release. I
however, I'm with the likes of Tom who prefer to see
things in lowercase most of the time. I guess that's what FORTRAN does to
one's brain after a while of trying to read it.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
diate thought. Unfortunately that means reinventing the
wheel; or grabbing it from BSD or somewhere and distributing it with
postgresql.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
On Fri, 28 Nov 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
>
> > $ time ./a.out 2>&1 | tee a.txt
> > out of order tv_sec: 1070066197 273140, prev 1070066195 721010
> > out of order tv_usec: 1070066197 273140, prev 107006
On Fri, 28 Nov 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > On Fri, 28 Nov 2003, Tom Lane wrote:
> >> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > On an Intel Linux 2.4.18 I get them quite oft
On Fri, 28 Nov 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > On an Intel Linux 2.4.18 I get them quite often, 25 in 1'45", but they
> > are all just a microsecond.
>
> What do you mean by "just a microsecond"?
On Fri, 28 Nov 2003, Tom Lane wrote:
> Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> > On November 28, 2003 12:33 pm, Tom Lane wrote:
> >> Whoa. Try the following test program. Then send it in to your friendly
> >> local BSD hackers
>
> > I've been running this code on a pair of FreeBSD
On Sun, 23 Nov 2003, Oleg Bartunov wrote:
> does tsearch2 in 7.4 still has the problem ? I apologies if we miss your
> patches but certainly we're interested in clear explanation of the problem.
The problem was memory allocations made through malloc and family were not
being checked for failure
Oops, sorry folks. That was only meant to go to Joshua.
On Sat, 22 Nov 2003, Nigel J. Andrews wrote:
>
> > However, I would love to see those patches.
>
> Sure. Should be in the archive. The version for 7.4 was submitted and applied
> ...
--
> However, I would love to see those patches.
Sure. Should be in the archive. The version for 7.4 was submitted and applied
pre-release but if you really do want the 7.3 runnable stuff I can send it. It
was only the unchecked returns from malloc and family patch in the snowball
directory. I thin
On 19 Nov 2003, Robert Treat wrote:
> I don't think *we* thought it was a hot button issue.. at least I
> certainly didn't when I initially responded. There is no need for you to
> apologize, in fact, I'll apologize for the list, we sometimes get a
> little heated on -hackers. Hopefully you've not
should be the case.
> It is purely a business thing, liability and the like.
>
> Sincerely,
>
> Joshua Drake
>
>
> Nigel J. Andrews wrote:
>
> >On Wed, 19 Nov 2003, Bruce Momjian wrote:
> >
> >
> >
> >>Marc G. Fournier wrote:
&
On Wed, 19 Nov 2003, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 19 Nov 2003, Michael Meskes wrote:
> >
> > > On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote:
> > > > I've been looking all over but I can't seem to see a company that is
> > > > providing *up-to-date* p
...
Does anyone actually read those messages?
Similar sort of question to the 'Does anyone read any of those popup boxes
produced by everything in Windows before hitting "OK"?' one.
--
Nigel J. Andrews
---(end of broadcast)---
On Sun, 5 Oct 2003, Gevik Babakhani wrote:
> Dear PostgreSQL masters,
>
> I know this might look like a childish question and you
> probably might have a good laugh over this but I
> would like to learn how PostgreSQL works inside-out.
> Could anyone please give me some pointers of where to star
ere core code, not optional, contrib
material, and one was running a 7.3 series server but wanted the nifty features
of tsearch2 instead of tsearch, would you expect all people upgrading within
the stable 7.3 branch for bug fixes to be forced to use tsearch2 and not
tsearch?
--
Nigel J.
On Mon, 29 Sep 2003, Christopher Kings-Lynne wrote:
> > So a db designer made a bloody mistake.
> > The problem is there's no easy way to find out what's missing.
> > I'd really like EXPLAIN to display all subsequent triggered queries
> > also, to see the full scans caused by missing indexes.
>
On Sat, 27 Sep 2003, Bruce Momjian wrote:
>
> OK, the thread test program is read for platform testing,
> src/tools/thread_test. You will find the README, Makefile tests, and
> program output to be very clear and almost error-proof.
>
> Please run it on platforms we support and report back. Th
you
should therefore be happy with the results or be prepared to live with them,
otherwise make sure what you're running.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
function?)
>
> No, Postgres can't do that.
But it can if you switch to one of the other languages like plpgsql, which
isn't terribly complicated but does require the language to be installed in the
database.
--
Nigel J. Andrews
---(end of broadcast)
On Wed, 24 Sep 2003, Bruce Momjian wrote:
> Nigel J. Andrews wrote:
> >
> >
> > I never knew running indent was so damn complicated. All three of my
> > development systems can not manage it without throughing a fault
> ...
>
> There are about 6 files tha
On Mon, 22 Sep 2003, Nigel J. Andrews wrote:
>
> There was a simple change commited in revision 1.47 of pgindent, listed as
> being "More updates for GNU indent".
>
> The questions are: why? and surely I can't be the only one whose hit this
> problem since No
re or there's a very strange
oddity that's been there, and specifically placed there, for nearly 2 years.
--
Nigel J. Andrews
#!/bin/sh
echo
echo -n Path=
echo $PATH
echo
# Known bugs:
#
# Blank line is added after, seen as a function definition, no space
# after *:
# y = (int) x
[I'm not convinced this is a -hackers issue so have cross posted to -general in
the expectation followups will go there]
I also didn't feel there was much I could cut from the earlier posts without
losing relevent info, so I didn't. Sorry.
On Fri, 19 Sep 2003, chakkara rangarajan wrote:
> Chris
On Thu, 24 Jul 2003, Francisco Figueiredo Jr. wrote:
> Nigel J. Andrews wrote:
>
> > On Tue, 22 Jul 2003, Francisco Figueiredo Jr. wrote:
> >
> >
> >>>How's this for an alternative if you really don't want any rows returned:
> >>>
ns behave like others when called as select *
> from voidfunction So I dont have to do select voidfunction. :)
But that last does exactly that. Doesn't even return a null. Give it a quick
go, skip the delete statement obviously, and see. You'll get something like:
?
---
(0
turns setof integer as '
begin
delete from blah;
return;
end;
' language 'plpgsql';
--
Nigel J. Andrews
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ng sql as the language and I don't know how that would
work.
Have you looked at plpgsql? Perhaps that is acceptable for you, in which case:
create function funcF ( ) returns integer as '
begin
delete from blah;
return null;
end;
' as language 'plpgsql';
select * fro
l
> when processing a request are stored in the same partition as the
> database in use. What about "/tmp" or other partitions? Maybe
> a set of other directories could be designated for this purpose?
>
> Hope this help... at least to add new items to the postgresql todo list;-)
>
> Have a nice day,
>
>
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tue, 22 Jul 2003, Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > OK. I'll suggest people to try new tsearch2 in README file of old
> > tsearch.
>
> Okay, that works for me. Please patch the old tsearch README file in
> both HEAD and REL7_3_STABLE branch as soon as possible --
On Sun, 20 Jul 2003, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > VERBOSE doesn't seem like the right name for the \set parameter.
>
> VERBOSITY would be okay with me.
>
Sounds meaningful. I often want to say 'verbosity level' when tal
you're wondering where the 42xxx error codes came from,
> I borrowed them from DB2. The SQL99 spec seems happy to lump
> all sorts of conditions under 42000 "syntax error or access
> violation" ...)
Looks good. Error codes are always handy to have and the extra
he lines of "whatever you
put on here we own it's just we tend not to persue that at the moment as
there's not much money in it for us but that doesn't stop us from claiming it
at some indeterminate time in the future"?
--
Nigel J. Andrews
---(
going to apply their own acceptance
testing anyway. If you think that doesn't happen you try sitting through 2
solid days of Y2k testing on _one_ system and tell me customers never do their
own testing.
> Therefore, I am going to stop harping on it.
But there is no need to, as has been mentioned before, if the testing is not
upto your level of testing submit something that makes it so. Having said that
I do believe you mentioned that you didn't have the time to create something
but you would be happy to test it, i.e. test the test.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Thu, 19 Jun 2003, The Hermit Hacker wrote:
> On Thu, 19 Jun 2003, Andrew Dunstan wrote:
>
> >
> > Maybe a better strategy would be to get a release out soon but not wait
> > 6 months for another release which would contain the Win32 port and the
> > PITR stuff (assuming those aren't done in t
and not to provide normal workspace for them.
Having said all that, I haven't read the start of this thread so I've probably
missed the reason for the complaint about lack of swap space, like a problem on
a small memory system.
--
Nigel J. Andrews
---(end of
On Tue, 10 Jun 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > How do people feel about changing matching for host and hostssl to be such that
> > a plain host line in pg_hba.conf does not allow a SSL connection but requires
> > t
On Mon, 9 Jun 2003, Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > Hey, I'm looking at the postgresql.conf.sample in CVS, and can't find the
> > option that's supposed to let you turn off "Inserting missing FROM clause for
> > table ..."
>
> Bruce hasn't applied that patch yet. I
How do people feel about changing matching for host and hostssl to be such that
a plain host line in pg_hba.conf does not allow a SSL connection but requires
the hostssl specifier?
I had been going to submit a very small patch to do this but then it occurred
to me this was a good candidate for a
Note, primary list address changed to -general, I'd suggest any followups
remove the -hackers, which I've left in just for 'closure'.
On Fri, 6 Jun 2003, Nigel J. Andrews wrote:
> On Fri, 6 Jun 2003, Tom Lane wrote:
>
> > "Nigel J. Andrews" <
been lost in a hole
somewhere much like another of my posts.
On Sun, 8 Jun 2003, Nigel J. Andrews wrote:
>
> Note, primary list address changed to -general, I'd suggest any followups
> remove the -hackers, which I've left in just for 'closure'.
>
>
> On F
On Fri, 6 Jun 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > Now, I did a little bit of testing and when doing a \lo_export
> > in psql connected via localhost a SIGPIPE is generated in
> > write() in libc and psql quit
bytes are returned and cmp shows no
differences to the original.
So, a) is this known? b) what is it? c) is it not going to happen in the new
protocol? and d) does anyone care?
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
hat with RPMs I was doing it properly from source.
Those RPMs are dangerous, they turn you mind off.
I voted for setting 'C' by default.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
led dba_1
then if you do:
alter user dba_1 set autocommit to off;
whenever you log in as the dba_1 user you will find that the autocommit is
turned off.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
can be referenced in a foreign key then a uniquely identifies
a row in the referenced table and therefore a primary key of (a,b) necessarily
is unique based solely on a, i.e. the (a,b) combination seems unlikely to be
the primary key for the table.
>
> The workaround shown here
that I don't see why this facility can't be included in
addition to the existing scheme.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ed outside of where I say I want things placed.
That includes configuration files. Doing this as a normal user protects the
system from bad software which assumes things about the host system. It also
simplifies switching between versions of software, try doing that if your
config is /et
t; is
> 1 Gb, but does a large object constitute a field? :)
>
> Thanks,
> Paul
I don't know but large objects are stored in the filesystem so I presume any
limit is going to apply there. A large object isn't a field, the large object
id can, and very prob
When I first saw this thread I thought of the PHP docs which I recently started
using, from a level of knowing absolutely nothing of PHP.
Sure there was some useful stuff in some of the comments but some of the pages
were very long, far more comment than manual page. A lot of the comments refer
t
g lookups
> when restoring a prior setting during error recovery. That's still a
> valid concern, so right offhand I don't see an easy fix. Any ideas?
How about throwing an error if an all digit user name is given to create
user as already alluded to?
Seems that would be
it
means that the flaw only applies to the pserver method.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
gt; a general-purpose tablespace implementation.
Wasn't someone just about done with a tablespace implementation? I certainly
remember some discussion on this subject a few months ago.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
of:
SELECT a.blah, a.foo,
FROM a, b
WHERE a.blah = b.blah AND a.foo = b.foo AND b.oid IS NULL
if that doesn't use a query try pushing the null test into a subselect like:
SELECT a.blah, a.foo,
FROM a, (SELECT * FROM b WHERE oid IS NULL) b
WHERE a.blah = b.blah AND a.foo = b.foo
After that let's hope I haven't embarrassed myself.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
FWIW, a search on Google gives some hits for the name on the lists this
year.
First impressions are that it's not Sir Mondred (or whatever the spelling was).
On Tue, 26 Nov 2002, Justin Clift wrote:
> Hi Chris,
>
> Just received this from them. Look like he was trying to claim stuff
> that
ase, which will be drafted in 2 days.
>
> If you have something to say, please e-mail me, Marc ([EMAIL PROTECTED])
> and Justin ([EMAIL PROTECTED]) off-list so we can quote you!
I think it's great - but don't quote me on that. :)
--
Nigel J. Andrews
---
e beta 3 mark but yes, built it
on a Debian 2.2 installation with no library upgrades or anything. Now of
course one would need a new bison.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an
On Wed, 13 Nov 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb 3 23:48:56 GMT 2000
>
> > with the expection of:
> > [snipped]
> > in t
4,220
SET f1 = FLOAT8_TBL.f1 * '-1'
WHERE FLOAT8_TBL.f1 > '0.0';
SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
! ERROR: floating point exception! The last floating point operation either exceeded
legal ranges
or was a divide b
memory
correctly.
Hmmm...there do seem to be a few mallocs in plpython.c . I haven't looked very
closely but nothing jumped out at me as being obviously wrong from the grep
output.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 5: Ha
ever, that would just be making
life way too awkward, bearing in mind the above paragraph. Can't we get Sir
Mongle (or whatever the name was) to test these things under the auspices of
them being DoS attacks?
--
Nigel J. Andrews
---(end of broadcast)
On Sat, 19 Oct 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > The leak is that memory is grabbed in SPI_prepare() for a plan within
> > whatever context is current when it does the palloc(). It may be the
> > caller's or it may
appen when the plan variable is
reassigned. However I was baffled why the process still had an obvious memory
leak so looked a little closer at SPI.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
anything non alphanumeric
but then I'm not sure about internationalisation and that test.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROT
On Thu, 3 Oct 2002, Bruce Momjian wrote:
> Nigel J. Andrews wrote:
> > cvs diff -r HEAD pltcl.c
> >
> > gave me differences against revision 1.64
> >
> > and cvs update pltcl.c
> >
> > said it was merging changes between 1.64 and 1.61
> >
On Thu, 3 Oct 2002, Bruce Momjian wrote:
> Nigel J. Andrews wrote:
> >
> >
> > I've been waiting to see how a patched file differs from my version.
> >
> > The patch was added to the to apply list last week I think (it wasn't mine btw)
> > and
there a problem with the anoncvs archive?
--
Nigel J. Andrews
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ed as '0'.
So what would I be selecting in Oracle if I did:
SELECT * FROM mytable WHERE myfield = ''
where myfield is of VARCHAR type?
If you want to select on NULL, whether or not you think the database is more
intelligent than you in determining what you really want, then wr
oning that
I've straightened this out in my brain a bit more.
On Wed, 25 Sep 2002, Nigel J. Andrews wrote:
> On 25 Sep 2002, Neil Conway wrote:
>
> > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > > Yes, I do get the similar results.
> > >
>
On 25 Sep 2002, Neil Conway wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > Yes, I do get the similar results.
> >
> > A quick investigation shows that the SPI_freetuptable at the end of
> > pltcl_SPI_exec is trying to free a tuptable of v
#x27;ve been reading that test
function wrong, it's got a level of nesting.
Unfortunately, I am currently trying to throw together a quick demo of
something at the moment so can't investigate too fully for the next day or so.
If someone wants to pick this up feel free otherwise I'll l
notion of making XLOG location more
> easily configurable --- it was just the notion of making it depend
> on environment variables that scared people.
And it's obvious it was centred on the use of an environment variable from the
subject line, it's still g
fore there were warnings. Can anyone comment on the correctness of this?
Reversing my changes doesn't really help matters so I presume it is something
else that is causing the different behaviour.
--
Nigel J. Andrews
On Fri, 20 Sep 2002, Nigel J. Andrews wrote:
> On Thu, 19 S
e just as in the pltcl patch I submited
earlier (which I can't remember if I've seen in the list so I may well resend).
However, the comments in the code imply there might be another leak with
prepared plans. I'm looking into that so I won't be sending this patch just
yet.
--
aspect strange. That's 1 second
(approx.) per row retrieved. That is pretty dire for an index scan. The
data/index must be very non unique.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ps, and fix the disk/controller.
Could possibly be a filesystem error but even if so it's still casting doubt on
the hardware. On the other hand I do believe I saw a message recently saying
that some of the 2.4 series kernels had file system bugs. I don't know which,
someone
function which triggers
> the problem.
I can probably take a look at this tomorrow, already started by looking at the
pltcl_SPI_exec routine. I think a quick glance at ...init_unknown() also shows
a lack of tuptable freeing.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
eks old
now being from the day before beta freeze.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
x27;t it be best to
see what happens there before creating the TODO item for the log?
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
s, and sorry for adding to people's email and work load.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
/*
* Derived from tablefunc.c, a sample to demonstrate C functions which
* return setof scalar and setof composite by Joe Conway <[EMAIL PROTE
On Tue, 3 Sep 2002, Karel Zak wrote:
> On Tue, Sep 03, 2002 at 12:28:37PM +0100, Nigel J. Andrews wrote:
> >
> >
> > It's probably a pretty basic question explained in some document I haven't seen
> > but...if I do something like a CreateTupleDescCopy() how
It's probably a pretty basic question explained in some document I haven't seen
but...if I do something like a CreateTupleDescCopy() how do I know my memory
context owns everything allocated without following the code all the way
through until it returns to me?
--
Nigel
On Sun, 1 Sep 2002, Marc G. Fournier wrote:
> On Sun, 1 Sep 2002, Nigel J. Andrews wrote:
>
> >
> > On Mon, 2 Sep 2002, Gavin Sherry wrote:
> >
> > > On Sun, 1 Sep 2002, Nigel J. Andrews wrote:
> > >
> > > > When is the beta freeze?
>
On Mon, 2 Sep 2002, Gavin Sherry wrote:
> On Sun, 1 Sep 2002, Nigel J. Andrews wrote:
>
> > When is the beta freeze?
>
> Today.
>
Oops, my fault for being imprecise.
I was wondering what time of day with timezone. Someone suggested end of today
but that means differe
my time and effort at the moment.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
7;old school' types. I use
find | xargs grep
often followed by tags in Emacs.
It isn't perfect but then I'm not either.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
_length is something sensible like word_length I presume.
That sizeof(int32) should really be VARHDRSZ imo, but I can't see how that's
breaking it.
Disclaimer: I have no idea what I'm doing here.
--
Nigel J. Andrews
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Mon, 26 Aug 2002, Bruce Momjian wrote:
> Tom Lane wrote:
> > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > > I was taking the line that the last slots in the array are
> > > reserved. Those are not going to be taken by non su connections.
&g
On Mon, 26 Aug 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > + if (!superuser() && MyBackendId > MaxBackends - ReservedBackends)
> > + elog(ERROR, "Normal user limit exceeded");
>
> This codin
can be taken by connections that subsequently
lose superuser priviledges thus evading the lower limit on backends.
Passed regression tests, not that it was likely not to.
Behaved as expected in a manual test.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
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
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 a
r the record, this is related to reserving the last few backend slots for the
superuser and I just need to test what I've done.
TIA
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP
peed on the internals. Your proposal is that cstring etc. get entries like
record on pg_type? That presumably means we'd need in and out functions defined
for these, which in the case of cstring would just be copying the input to
output?
(As you can see I may not be the best person to work on
On Tue, 20 Aug 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> >> I'd like to see something done about this fairly soon, but it's not
> >> happening for 7.3 ...
>
> > Does anyone have an idea about what other funct
functions are affected by this?
As a stop gap measure to remove the *known* DoS issue how about changing the
pg_proc entry to restrict input types, i.e. not cash_out(opaque)? cash_words is
already listed as only taking the money type is cash_out really that different?
On a related topic cash_out(
oup writable world not I presume.
I wouldn't even know how to port that to un unixy systems like Win32.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
romise: database@username ?
[BTW, I did check and '@' seems to be a valid character in database and user
names.]
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
to check this out. I
for one was completely unaware of those 64 bit functions.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregiste
far off getting to 4GB and can the host system handle such
files?
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
1 - 100 of 119 matches
Mail list logo
