(US style) assume DD before MM, and then reject
if out of range, rather than allowing the range to determine which is
which.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
them up in
a window; sending to stderr is likely to mean sending to /dev/null,
or at best a logfile that the user will never look at.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
(with a note about why).
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
for that ASAP.)
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Joe Conway [EMAIL PROTECTED] writes:
Attached is a patch for the issue reported above by Nabil. Please apply.
Applied (with correct spelling ...)
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists
, or is it just a Source Developer Option?
It's gone. You might want to crosscheck the docs against the CVS-tip
version of guc.c ...
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
...
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
. Then it would be
practical to recover the memory associated with an obsoleted cache
entry. But we've lived without this so far, so I guess it's not causing
many people problems.
regards, tom lane
---(end of broadcast)---
TIP 5: Have
?
Applied.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Joe Conway [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm not excited about picking a notation for the long term on the
grounds that it takes the least code to implement today.
I knew you wouldn't be ;-)
I admit I have not got a clearly-better solution in my hip pocket,
but $0 is just
be the set of tested values? I have it as
buffers: first to work of 1000 900 800 700 600 500 400 300 200 100 50
connections: first to work of 100 50 40 30 20 10
but we could certainly argue for different rules.
regards, tom lane
*** src/backend/port/sysv_shmem.c.orig
it.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
to cope with this.
I disagree with the concept of expecting someone to supply useful values
at install time anyway, since a newbie is the *least* likely to have any
idea what to say at that time. Heck, the experts can hardly agree on
what to use ...
regards, tom lane
this unless you want to
make it interactive, which would certainly make the RPM guys really
unhappy.
I'd rather see such considerations pushed off to a separate tool,
some kind of configuration wizard perhaps.
regards, tom lane
---(end of broadcast
Kenji Sugita [EMAIL PROTECTED] writes:
This small patch eliminates relations in information_schema from oid2name
listing.
Seems like it'd be a good idea to eliminate views and composite types as
well.
regards, tom lane
---(end of broadcast
that
it was originally told to unlink, regardless of what happens to those
globals.
If you are intent on spending code to free stuff just before the
postmaster exits, a better fix would be for UnlinkLockFile to free its
string argument after using it.
regards, tom lane
the change as a matter of
future-proofing that routine against such use. But on the argument of
preventing resource leakage today, this is just a waste of code space.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9
, and
I'm not having any luck finding that message in the archives right
now. Sumit, did you keep a copy?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
there are no other paths for parsing a date spec in the main
date/time code?
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Kris Jurka [EMAIL PROTECTED] writes:
On Fri, 25 Jul 2003, Tom Lane wrote:
I'm not having any luck finding that message in the archives right
now. Sumit, did you keep a copy?
http://groups.google.com/groups?hl=enlr=ie=UTF-8selm=28882.1057162309%40sss.pgh.pa.us
Thanks, but that actually
we can get away with deciding that common date
formats aren't common.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Bruce Momjian [EMAIL PROTECTED] writes:
Tom, how do I pass PG_FUNCTION_ARGS to another function, while adding a
new parameter?
I wouldn't. Do the PG_GETARGS in the wrapper, and have the called
function take a normal C parameter list.
regards, tom lane
and application. The comment wouldn't have prevented the
error, because patch(1) can't read comments.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
adding one.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
tip or a nightly
snapshot tarball should be pretty-durn-close-to-the-beta.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
I don't understand what the diffs in postgres.c are supposed to
accomplish, but I can just about promise that they are misplaced too,
since they won't affect queries executed via functions or SPI.
regards, tom lane
---(end of broadcast
moves the core dump
somewhere else, unless you find reasonable fallbacks for *all* its
callers (including applications you don't have the source code for,
but in any case including every one of the calls in libpq).
regards, tom lane
---(end
+ ((-1.0::float8) + 1.0e-20::float8);
?column?
--
0
(1 row)
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Bruce Momjian [EMAIL PROTECTED] writes:
This has been saved for the 7.5 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
Saved for? It's not gonna be acceptable in its current form for 7.5,
either.
regards, tom lane
---(end
[ followup to old message ]
Greg Stark [EMAIL PROTECTED] writes:
This patch adds an autoconf test to check for the new incompatible version of
flex.
Peter E. claims that CVS tip does work with flex 2.5.31 --- so we
shouldn't need this patch anymore.
regards, tom lane
; it will usually behave reasonably when it runs out of memory for
a query result. If you'd like to pursue the matter, please pull down
CVS tip and see what you can do with it. The patch as given would not
be much use to us anyway because of the changes since 7.3...
regards, tom lane
, and for integers on bigendian machines, but
not for much else.)
We are not going back to the pre-7.4 format. Sorry.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
tuple should be said to be IS OF the tuple type
of its parent). And what about domains --- should we say a domain type
IS OF its base type?
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
assumption; the question was just about
whether your code acts sanely if the assumption isn't true.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
Joe Conway [EMAIL PROTECTED] writes:
Here's a patch for the documentation updates. Please apply.
Applied with one small change --- I thought the last example failed
to make the point that the elements of an ARRAY[] construct could be
dissimilar.
regards, tom lane
of the changes didn't apply cleanly,
and seemed unrelated anyway. This fixes the immediate complaint, but
if there's some reason to apply the rest to 7.3.*, would you submit
an additional patch against that branch?
regards, tom lane
---(end of broadcast
Karel Zak [EMAIL PROTECTED] writes:
Hmm.. but the patch fix another small bug which I found today.
Okay. Please send a patch against 7.3 tip and I'll throw it in.
regards, tom lane
---(end of broadcast)---
TIP 2
Karel Zak [EMAIL PROTECTED] writes:
Hmm.. but the patch fix another small bug which I found today.
Okay. Please send a patch against 7.3 tip and I'll throw it in.
The patch for REL7_3_4 is attached.
Applied, thanks.
regards, tom lane
Janko Richter [EMAIL PROTECTED] writes:
On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with:
Yeah, it's broken on any system with shmmax too small for the
defaults :-(. My fault.
This patch solves the problem:
It's fixed in a different way in CVS tip.
regards, tom
misspellings of language
names.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
in the
main description in runtime.sgml, which are all upper case. That is a bit
inconsistent, but I think it's OK, because here they sort of serve as
section titles.)
Okay, that seems reasonable. Ignore my prior message --- I hadn't come
across this one yet.
regards, tom lane
Bruce Momjian [EMAIL PROTECTED] writes:
Would you like me to conditionally add the IPv6 line to pg_hba.conf from
initdb now?
I was going to tackle that tomorrow, but if you wanna do it, go for it.
regards, tom lane
---(end of broadcast
to do this, what is it?
regards, tom lane
---(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
fixed that yesterday.
The s_addr name collision is unfortunate, but easily worked around;
fix committed as suggested by Larry.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives
?
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
months''P1Y6M'
'3 hours 25 minutes 42 seconds' 'PT3H25M42S'
Er, don't we support that already? I know I saw code to support
something much like that syntax last time I looked into the datetime
routines.
regards, tom lane
---(end
to make sense, it's
likely a bug rather than anything we want to preserve. In particular,
given the knowledge that it doesn't meet the ISO spec, I'd judge that
the existing code for the ISO shorthand was a work-in-progress.
regards, tom lane
---(end
.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
assumed Oleg and Teodor would
take care of it. But they haven't yet, so I applied what I could.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
probably have a better feel for this than
I do, but I just wanted to point out that there was *some* thought
behind doing it this way. I'm fine with changing it if other
translators agree it's better.
regards, tom lane
---(end of broadcast
, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
stuff
seemed completely obsolete, but intagg isn't.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
the above is unhelpful by any measure.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
types.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through
Manfred Spraul [EMAIL PROTECTED] writes:
Tom Lane wrote:
This patch is missing a demonstration that it's actually worth anything.
What kind of performance gain do you get?
7.4cvs on a 1.13 GHz Intel Celeron mobile, 384 MB RAM, Severn RedHat
Linux 2.4 beta, postmaster -N 30 -B 64, data
because log_duration is set,
we don't need to print it again if the duration of the query exceeded
log_min_duration_statement), but I haven't changed it.
I think there should be just one duration: nnn log entry, printed if
either condition holds.
regards, tom lane
. Sigh.
regards, tom lane
---(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
. But vacuumlo shouldn't depend
on it.) I've applied a patch.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
other names for
the null character.
In short, I think most of this patch is just pedantry. Could you
trim it down to just the places where there's actually risk of
confusion? (I do agree that upper case NULL is not appropriate as
a name for the character.)
regards, tom lane
.
regards, tom lane
---(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
.
regards, tom lane
---(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
than moving information around depending on which
combination of switches happens to have caused the log entries to be
generated. Am willing to fix the code to make this happen.
regards, tom lane
---(end of broadcast)---
TIP 1
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
I would prefer to see the log entries look like
LOG: query: select * from pg_class;
LOG: duration: nn.nnn msec
The problem with two lines is that another log message could get between
them.
That was true already with log_statement
lines together, then we have got lots
bigger problems to fix than log_duration. I'm not convinced it's an
appropriate goal at all, though.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free
,
which would tip you off?)
I think this is a red herring.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
BTW, EXPLAIN ANALYZE puts out
Total runtime: 406.53 msec
Do you want to make an exception to the string freeze to change this
to ms?
I just realized, all the things that are sent as a query result instead of
an error or notice
[EMAIL PROTECTED] writes:
Also I'd love to see the log_query being settable per database...
AFAIK you can do that now.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
position considerably. It needs a little
thought as to whether this would induce any confusion, and whether we
really care if so.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose
Bruce Momjian [EMAIL PROTECTED] writes:
Another example:
LOG: duration: 4.228 ms; select *\nfrom pg_language;
Minor quibble: would it read better as
LOG: duration n.nnn ms: query
or
LOG: duration n.nnn ms for query
regards, tom lane
in making the log easy to
process.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
for one line per part, viz
ERROR: blah blah blah
DETAIL: blah blah\nblah blah
HINT: blah blah\nblah blah\nblah blah
but perhaps someone would like to argue for somehow collapsing all this
to one line? If so, how exactly?
regards, tom lane
, we add a tab after any newline,
That's a thought... seems less invasive than the backslashing. Not sure
how well it'll work for syslog output though.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all
HINT: something else
No, one would hope no tab before DETAIL/HINT/etc. The idea is to be
able to recognize when the contents of one of these entries spans lines.
regards, tom lane
---(end of broadcast)---
TIP 4
move.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
not worry about code motion around a
MemSet call, since that would require the compiler to prove that the
memset() path through the macro wouldn't be affected, which I doubt it
would think.
regards, tom lane
---(end of broadcast
),
becomes
! printfPQExpBuffer(buf, _(\%s\ %s),
but ISTM the latter string doesn't really need any translation and so
it wouldn't be much of a problem.
Comments?
regards, tom lane
---(end of broadcast
.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
Given that gcc is smart enough not to move any code across the memset()
call,
Is it?
It had better be.
regards, tom lane
---(end of broadcast)---
TIP 8
possibly optimize away the alignment test ...)
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
Manfred Spraul [EMAIL PROTECTED] writes:
Tom Lane wrote:
Is gcc 3.3 smart enough to optimize away the pointer alignment test
in the full macro?
3.2 optimizes away the pointer alignment test, but then doesn't pipeline
the x*x calculation.
Hm, confirmed here. So indeed it seems that Bruce
...
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
to 2.7.something, which is pretty much
ancient history now --- and if anyone needs to make it work with such an
old gcc, all they need do is specify CFLAGS to configure instead of
letting it default.
Will commit this change unless I hear objections soon.
regards, tom lane
would fix that, since it sure looks like an optimization bug, but
evidently not.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
Would we be happy with the following, which would work ?
} while (z = 0 || z == MAX_RANDOM_VALUE);
I suppose this doesn't?
} while (z = 0 || z = MAX_RANDOM_VALUE);
regards, tom lane
.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
in *everything* being considered a system table?
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
.), so how about the attached patch?
Seems reasonable, but the patch ought to fix the comment just above,
preferably with the above observation that this is correct by
examination of the now-frozen 7.0 initdb code ...
regards, tom lane
---(end
so actually there has never been an assumption that c.h would include
fcntl.h generally. Okay, objection withdrawn.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
qualified functions? There might possibly be some issues in
contrib stuff, but there are no other SQL-language functions defined in
the main system (except information_schema, which we already checked).
regards, tom lane
---(end of broadcast
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
OK, I will test them all today and get back to you.
I checked them all before applying, but please do cross-check. We're
close enough to release that double- and triple-checking patches is
called for.
regards, tom lane
certain he realizes that he's got a very low number-of-connections
resource limit. Sweeping such problems under the rug is exactly what
make check should not do.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner
Johann Uhrmann [EMAIL PROTECTED] writes:
Tom Lane wrote:
Johann Uhrmann [EMAIL PROTECTED] writes:
... Therefore, only lines
beginning with Apache Ant version should be considered.
Do *all* versions of Ant identify themselves that way? I'd be inclined
to write
grep -i ant version
instead
+}
+__EOF__
+ $CC conftest.c /dev/null 21
+ if test $? = 0; then
+CFLAGS=-O -Kinline
+ else
+CFLAGS=-O -Kinline,no_host
+ fi
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
before we recurse.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Neil Conway [EMAIL PROTECTED] writes:
On Mon, 2003-11-03 at 10:04, Tom Lane wrote:
You have effectively reverted the code to its previous slow state.
Erm, the original version of this code in CVS (from ~7 years ago) is the
following:
Hm. I coulda sworn that at some point I changed that code
the second List, as later mods to either list could destroy
the invariant for the other list.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
the
problem for Tcl 8.0.*? Or will the unwanted character set translation
happen anyway in that version? I don't see any value in letting the
code compile against 8.0.* if the behavior will be wrong ...
regards, tom lane
---(end of broadcast
1 - 100 of 3478 matches
Mail list logo