wouldn't add more
features to it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Mike Rylander wrote:
A related question, however: Will the XML features being included in
8.3 support namespace prefix registration?
That is certainly the plan.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
weird.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
. The
use of memory allocation in the GUC code might still need some review.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe
is that the GUC code apparently makes
mixed used of palloc and guc_malloc, and this patch continues that.
I'm not sure if this is really well thought out.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3
Mike Rylander wrote:
The patch adds support for default XML namespaces in xml2 by providing
a mechanism for supplying a prefix to a named namespace URI.
How does it support multiple namespaces in one document?
--
Peter Eisentraut
http://developer.postgresql.org/~petere
Toru SHIMOGAKI wrote:
The attached is a doc patch for Linux memory overcommit and an
additional way of avoiding a problem that postmaster is suddenly
killed by OOM-Killer.
The text needs some articles.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
Toru SHIMOGAKI wrote:
The attached is a doc patch for Linux memory overcommit and an
additional way of avoiding a problem that postmaster is suddenly
killed by OOM-Killer.
Patch installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
format.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get
a similar
interface? is a Frequently Asked Question.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about
Bruce Momjian wrote:
I have implemented your ideas for checking BLCKSZ = 1024,
I think the check should be were the issue arises, not in some distant
file without explanation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
output that
validates against XML Schema schemas, and so we cannot pick the data type
formats outselves.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore
in that regard.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
Should we revisit xpath_array() for 8.3, or is this all in core
now?
Not yet, but we are currently discussing how.
Uh, was this handled?
Not yet.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
you rely on the LIMIT clause to do the same? Is there a
guarantee that LIMIT on a table function makes a consistent order?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
to provide, and it seemed reasonable to
me. I have no need for them personally.
David Fetter has also repeated failed to offer a use case for this, so I
hesitate to accept this.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
Bruce Momjian wrote:
Seems the consensus was this was a good idea, and not feature-creep.
I wonder whether we want this to read from the console, like the
password prompts, or from stdin. Not sure which is more useful.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
show a use case.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
, the project was doing some text processing
inside of postgres, and getting all of the words from a string into a
table with some processing (excluding stopwords and so forth) as
efficiently as possible was a big concern.
We already have tsearch for that.
--
Peter Eisentraut
http
Am Freitag, 16. Februar 2007 08:02 schrieb Jeremy Drake:
On Thu, 15 Feb 2007, Peter Eisentraut wrote:
I have no strong opinion about how matches are returned. Seeing the
definitional difficulties that you point out, it may be fine to return
them unordered. But then all matches functions
David Fetter wrote:
The question is, what is the use case? If there is one in Perl,
can this proposed function API support it?
Perl makes the following variables available in any regex match,
That is not a use case.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
of the functions I've seen in earlier
patches in this thread is that they return setof something. But in my
mind, regular expression matches or string splits are inherently
ordered, so an array would be the correct return type.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
a function as part of the core API, it is
also important that we offer a clean design that allows other users to
combine reasonably orthogonal functionality into tools that are useful
to them.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
matches functions should do that.
For the split functions, however, providing the order is clearly
important.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
Bruce Momjian wrote:
On these questions, we have to find out how Oracle handles it, but
your approach seems appropriate.
I don't think Oracle even has that. But personally I'd like to see
errors for invalid pattern combinations.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
Chad Wagner wrote:
This adds the ability to prompt for internal variable input, below
are examples:
test=# \prompt x
Enter value for x: 3
You can do this already approximately so:
\echo -n 'Enter value: '
\set x `read echo $REPLY`
Maybe one command is better, though.
--
Peter Eisentraut
shell you can read the required
variables beforehand and pass them into psql through arguments. So the
use case for reading variables during a psql script seems questionable
anyway (without conditionals, at least).
--
Peter Eisentraut
http://developer.postgresql.org/~petere
Bruce Momjian wrote:
Should we revisit xpath_array() for 8.3, or is this all in core now?
Not yet, but we are currently discussing how.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions
Neil Conway wrote:
What about a --enable-gprof (or --enable-profiling?) configure
flag? This could add the appropriate compiler flags to CFLAGS, enable
LINUX_PROFILE if on Linux, and enable the gprof/pid mkdir().
That would really only work for GCC, wouldn't it?
--
Peter Eisentraut
http
Pavan Deolasee wrote:
I had this in a different form, but reworked so that it matches the
doc patch that Teodor submitted earlier. I think it would be good to
have this information in the lock.h file as well.
Why would we want to have two redundant copies of the same information?
--
Peter
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
New log output will look like:
LOG: server process (PID 29304) was terminated by signal: Bus
error (10)
The colon doesn't make sense to me.
OK, it seemed strange to say signal Bus error (10) because
Tom Lane wrote:
I don't like that because it parenthesizes the most important part of
the message, which is a style-guideline violation at least in spirit.
How about
... terminated by signal 10: Bus error
I like that.
--
Peter Eisentraut
http://developer.postgresql.org
=Y
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
of writing it is significantly
more cumbersome, so I request that this be fixed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
Jim Nasby wrote:
Following that logic we should remove all data types that aren't
specified in ANSI.
Sure, if we were to arrive at some acceptable implementation of official
modules, that would make sense in some cases.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
Magnus Hagander wrote:
* NULL function pointer in SSL call cast to the correct pointer type
Why not write NULL?
In the alternative, declare the variable to have the right type to begin
with.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
to be some centrally organized consolidation of the various existing
attempts under a label of officiality.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
for
readability.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
will not be a
proper and robust representation of the original database, which would add
significant confusion and potential for error.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL
of this feature? At
the moment it sounds like This option does something fun, but we're
not sure what it is.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
. Compare pgcrypto -- certainly no one
needs all those encryption algorithms, but we offer them.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire
Bruce Momjian wrote:
I should have been clearer. I think having in the main server or
/contrib makes sense. Having data types external to our source tree
doesn't seem to work too well because of changes in our API from time
to time.
When has the API for data types ever changed?
--
Peter
to
confuse this with how pg_dump treats the argument.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
:: are not
portable, so this cannot be implemented in the first place.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Bruce Momjian wrote:
To get the new html dependency to work properly, I removed the
.SECONDARY tag from the Makefile. SECONDARY prevents missing files
from being built.
That is not what it does.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
Am Mittwoch, 10. Januar 2007 01:41 schrieb Bruce Momjian:
Peter Eisentraut wrote:
Bruce Momjian wrote:
? %-A4.tex-ps: %.sgml $(ALLSGML) stylesheet.dsl bookindex.sgml
? $(JADE.tex.call) -V texdvi-output -V '%paper-type%'=A4 -o $@ $
+ ifndef DRAFT
+ [EMAIL PROTECTED] -s
$(ALLSGML) stylesheet.dsl bookindex.sgml
$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=A4 -o $@
$ ifndef DRAFT
@cmp -s HTML.index.start HTML.index || $(MAKE) html $@
endif
It would much easier to just run the html rule before the other stuff.
--
Peter
Bruce Momjian wrote:
%-A4.tex-ps: %.sgml $(ALLSGML) stylesheet.dsl bookindex.sgml
$(JADE.tex.call) -V texdvi-output -V '%paper-type%'=A4 -o $@ $
+ ifndef DRAFT
+ [EMAIL PROTECTED] -s HTML.index.start HTML.index || $(MAKE) $*
+ endif
What is the point of that?
--
Peter
Bruce Momjian wrote:
+ ifndef DRAFT
+ [EMAIL PROTECTED] -s HTML.index.start HTML.index || $(MAKE) $*
+ endif
Why are you using $*? This isn't a pattern rule.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
))
else
! # run default 'all' rule
! [EMAIL PROTECTED](MAKE) DRAFT=Y html
! endif
endif
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
-f HTML.manifest *.html *.gif bookindex.skip
I don't see bookindex.skip mentioned anywhere else. Left over from a
previous version?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading
to generate output
with a proper index
When converting to XML, you probably don't want an index because it will
be built differently by the XSLT toolchain. It's not clear what we want
anyway.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
.
This expands at the time the makefile is read. You may get it to work
with
target:
$(if $(wildcard blah), this, that)
The following may be helpful:
http://www.gnu.org/software/make/manual/html_node/Reading-Makefiles.html#Reading-Makefiles
--
Peter Eisentraut
http://developer.postgresql.org
they are attached to are intermediate,
normally followed by latex runs.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
send a patch.
(Or maybe it did work right and I misjudged it, but it was mentally in
the way of all the other complications.)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0
Tom Lane wrote:
I'm wondering how this got into the TODO list. It seems rather
pointless, and likely to create client compatibility problems (if
not, why is NAMEDATALEN exported at all?)
I think because it used to be used in libpq's notification structure.
--
Peter Eisentraut
http
directory, so I'd just
call it --xlogdir, parallel to --datadir.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
most of the parser work. What is left
hereafter is adjusting all the corner cases, the escaping rules, and
the various XML parser behaviors.
Use configure --with-libxml to build.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
xml-patch-20061219.bz2
Description: BZip2 compressed
whereas enums would be part of the type system used to model the data.
An objection to enums on the ground that foreign keys can accomplish the
same thing could be extended to object to any data type with a finite
domain.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
xml.sql shows some of the things that work.
This patch already covers most of the parser work. What is left
hereafter is adjusting all the corner cases, the escaping rules, and
the various XML parser behaviors.
Use configure --with-libxml to build.
--
Peter Eisentraut
http
build environment. Something is wrong here. Either the dtrace
documentation or ours.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire
Jim Nasby wrote:
As a less invasive alternative, I *think* you could create an SQL
function for casting text to int that treated '' as 0, and then
replace the built-in CAST with that.
Won't work. You need to replace the data type input function.
--
Peter Eisentraut
http
Am Donnerstag, 26. Oktober 2006 19:47 schrieb Neil Conway:
Note that this patch breaks the translations of these strings, so I
haven't applied it yet. Should I apply it now, or wait for 8.3 to
branch?
I appreciate this effort, but I think it's better to hold the patch.
--
Peter Eisentraut
Guillaume Lelarge wrote:
Guillaume Lelarge a ecrit le 12/10/2006 20:20:
Peter Eisentraut a écrit :
We should also support a format for ISO day-of-the-year, which
might be 'IDDD'.
I will work tomorrow on this one.
Don't we already have it ? It seems ISO day-of-the-year is between
001
not sure we can fix that, but I wanted to point
it out.
We should also support a format for ISO day-of-the-year, which might
be 'IDDD'.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our
Am Dienstag, 12. September 2006 12:53 schrieb Dave Page:
The attached micropatch fixes the README install for contrib/sslinfo.
Done, thanks.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't
to add
this now.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
the
XML syntax into 8.2, operating on text data. That will change when the xml
type goes into 8.3. So we'd be adding a feature right now with the
announcement that the feature will break incompatibly in the next release.
That doesn't seem very useful to me.
--
Peter Eisentraut
http
is.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
David Fetter wrote:
This patch clarifies the 'predicate locking' section in the docs.
What it does it raise the question what next-key locking is.
I don't think any of this matters for us. We should just remove the
part that claims that no other system implements predicate locking.
--
Peter
, expecting the system to
regenerate them when the view is reloaded?
Right.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe
--- it will give the wrong answers in the presence of
volatile functions such as nextval().
I'm not sure why anyone would want to define a view condition containing a
volatile function. At least it wouldn't put a major dent into this feature
if such views were decreed not updatable.
--
Peter Eisentraut
between ; and \g.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
Alvaro Herrera wrote:
I just detected another problem with building ecpg in a VPATH
environment. This patch fixes it for me.
I think you will find that $(top_builddir)/$(subdir) is equivalent
to .
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
Am Freitag, 25. August 2006 17:03 schrieb Martin Atukunda:
hmm, setting HISTFILE to /dev/null doesn't work on my MacOSX here.
Please elaborate on doesn't work.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
, then I
don't believe in the merit of the patch.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
, this is
for queries with large result sets. I'd guess that people will not normally
look at those result sets interactively. If the target audience is instead
psql scripting, you don't really need the most convenient command possible.
A \set variable would make sense to me.
--
Peter Eisentraut
http
Tom Lane wrote:
BTW, \u seems not to have any mnemonic value whatsoever ... isn't
there some other name we could use?
Ever since pgsql-patches replies started going to -hackers, threading
doesn't work anymore, so I for one can't tell what this refers to at
all.
--
Peter Eisentraut
http
beginning to think that VALUES might be a separate command after all.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index
the refactoring.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
-general
1.a. solicit comments
2. put information page on web site
3. link from documentation to web site
You seem to have short-circuited all that.
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
and
random white space changes is a pretty optimal way to get your patch
rejected. Please submit patches for these items separately.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze
Here is a preliminary patch for units in postgresql.conf (and SET and so on,
of course). It currently supports memory units only. Time units would be
similar. Let me know if you have comments.
(FWIW, work_mem is a good parameter to play with for trying this out.)
--
Peter Eisentraut
http
Am Montag, 24. Juli 2006 16:55 schrieb Stephen Frost:
#2: That variable can *not* be changed by a reload.
Notice-level message is sent to the log notifying the admin that the
change requested could not be performed.
This already happens.
--
Peter Eisentraut
http
Joachim Wieland wrote:
On Mon, Jul 24, 2006 at 07:09:17PM +0200, Peter Eisentraut wrote:
Am Montag, 24. Juli 2006 16:55 schrieb Stephen Frost:
#2: That variable can *not* be changed by a reload.
Notice-level message is sent to the log notifying the admin
that the change requested
Joshua D. Drake wrote:
Updated to have stronger wording for vacuuming. Cleaned out some
extra superlatives. Added a couple of index entries for Routine
Maintenance and added entry specific to Analyze.
diff -c please.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
-bin/cvsweb.cgi/libc/stdlib/qsort.c?rev=1.12content-type=text/x-cvsweb-markupcvsroot=glibc
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
is actually a mergesort in glibc ...
The merge sort is here:
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/stdlib/msort.c?rev=1.21content-type=text/x-cvsweb-markupcvsroot=glibc
It uses alloca, so we're good here.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
the function tries to scan some other table: if we ignored
that transaction, then another lazy vacuum might delete tuples from that
table that we need to see.
Functions in the index expression must be immutable, so I don't think that is
a real concern.
--
Peter Eisentraut
http://developer.postgresql.org
with this work and the xpath stuff in
contrib. Plus, there were a few rejected projects about creating
special index support for XML.
Whether or not this part is really useful I can't judge, but it's part
of an overall system.
--
Peter Eisentraut
http://developer.postgresql.org/~petere
of
objects would be really appreciated.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED
linked with
OpenSSL is sufficiently low that they do not have to worry about it.
Debian tends to be much more conservative in this regard, partly
because the risk is borne by third parties (e.g. mirror operators and
CD vendors).
--
Peter Eisentraut
http://developer.postgresql.org/~petere
. Currently PAM and NSS must be using the same
version of libpq as any program that might call them or everything
blows up.
Symbol versioning only helps if a function's signature has changed, doesn't
it? Have we ever done that?
--
Peter Eisentraut
http://developer.postgresql.org/~petere
is this: You are going to enter a world of pain.
If you are worried about mistyping options, I recommend setting up a shell
alias.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our
(and maybe variables?) but not
structs. Nothing helps in that case.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
or printing warnings or printing a
summary at the end, but we are not in a position to redefine build system
practice.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
/support/coin_faq/#extension_MSVCproject now, it
seems they have changed to autogenerating a project file as well. But
check there anyway; these guys have been doing this for years.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast
start to stop to reload etc.
without having to remove or rewrite all the options that are not really
relevant for that particular operation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you
the better term than variable.
If that is confusing, make it config_param or something like that.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
Bruce Momjian wrote:
Peter Eisentraut wrote:
Simon Riggs wrote:
pg_ctl -D test -U foo start
pg_ctl -D test -W start
pg_ctl -D test -w stop
pg_ctl -D test -l fast stop
etc.. (16 possible error combinations in total now checked)
I object to making these throw an error
101 - 200 of 657 matches
Mail list logo
