Hello
I thinking about more restrictive query and expression checking than
now. Used parser checking isn't enough - so some possible bugs can be
detected in production stage. Other problem is using any expression
as SELECT expr. The request on validation can be different and it is
probably for
Rob Newton írta:
Hi Hackers,
I posted this to the GENERAL list a while back, but got no repies.
Perhaps someone here can help...
I've been building ECPG (embedded SQL/C) programs on a system with Pg
version 8.0 installed. When I tried to run them recently on version
8.4 I found that there
On Tue, Feb 16, 2010 at 6:20 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Another possibility is to force a ProcessIncomingNotifies scan to occur
before we reach ReadyForQuery if we sent any notifies in the
just-finished transaction --- but that won't help if there are
uncommitted messages in front
You might want to try setting log_autovacuum_min_duration=0 in the
postgresql.conf
Thanks, tried it. There is nothing in the log - the actual
vacuum/analyze commands are not run (as there is no query activity). I
suspect that autovacuum is checking each database if it should run - and
2010/2/16 Takahiro Itagaki itagaki.takah...@oss.ntt.co.jp:
Pavel Stehule pavel.steh...@gmail.com wrote:
The dictionary data could be shared or minimally dictionary could be
preloaded like some PL language.
What do you think about this?
Surely preloading is the most realistic approach, but
Folks,
Would it be worthwhile to light up some buildfarm animals on OpenVMS?
http://www.openvms.org/stories.php?story=10/02/09/2319162
Cheers,
David.
--
David Fetter da...@fetter.org http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP:
On Tue, Feb 16, 2010 at 09:44:26AM +1000, Rob Newton wrote:
I posted this to the GENERAL list a while back, but got no repies.
Perhaps someone here can help...
Didn't see it there, sorry.
Then I noticed libecpg_compat in the lib area. What is this used
for? compat suggests compatibility
Arie Bikker wrote:
Hi all,
I've combined the review suggestions of Jan Urbański, Scott Bailey, and
others.
This was a lot harder, then I had foreseen; and I took my time to do it
the right way (hope you agree!).
Hi,
I see the patch has been marked as Returned with Feedback on the 6th
of
Hi,
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not initialized (i.e.,
SetTransactionIdLimit() is not called) until VACUUM is
On Tue, Feb 16, 2010 at 12:37 AM, Magnus Hagander mag...@hagander.net wrote:
With the libpq fixes, I get further (more on that fix later, btw), but
now I get stuck in this. When I do something on the master that
generates WAL, such as insert a record, and then try to query this on
the slave,
2010/2/16 Fujii Masao masao.fu...@gmail.com:
On Tue, Feb 16, 2010 at 12:37 AM, Magnus Hagander mag...@hagander.net wrote:
With the libpq fixes, I get further (more on that fix later, btw), but
now I get stuck in this. When I do something on the master that
generates WAL, such as insert a
On Tue, Feb 16, 2010 at 2:48 AM, Robert Haas robertmh...@gmail.com wrote:
Multiplying by the block size makes it sound as if all the
memory was read or used, which is simply not the case - especially for
things like buffer hits, which don't actually read or allocate any
memory at all.
In
Hi,
buildfarm member pika fails the NaN test.
Does FreeBSD/MIPS really return true for isinf(NaN)?
Anyway, the attached patch tries to fix the test case
by testing isnan() first and doesn't check isinf()
if isnan() returned true.
Best regards,
Zoltán Böszörményi
--
Bible has answers for
Boszormenyi Zoltan írta:
Hi,
buildfarm member pika fails the NaN test.
Does FreeBSD/MIPS really return true for isinf(NaN)?
Anyway, the attached patch tries to fix the test case
by testing isnan() first and doesn't check isinf()
if isnan() returned true.
I lied in the patch name, it
On Mon, Feb 15, 2010 at 02:58:47PM -0800, David E. Wheeler wrote:
On Feb 15, 2010, at 2:42 PM, Tim Bunce wrote:
I've not really looked the the DBD::Pg code much so this seemed like a
good excuse... It looks like the default is to call PQprepare() with
paramTypes Oid values of 0.
Yes,
Just a heads-up really - following discussion with Magnus and other
people involved in building our Windows packages, I intend to stop
including MIT Kerberos support from 9.0 onwards. This is largely due
to the fact that most (maybe all) users are more likely to use SSPI on
Windows, and more
Tom Lane wrote:
We could adopt the historical policy of sending self-notifies
pre-commit, but that doesn't seem tremendously appetizing from the
standpoint of transactional integrity.
But one traditional aspect of transactional integrity is that a
transaction always sees *its own*
On Tue, Feb 16, 2010 at 7:20 PM, Magnus Hagander mag...@hagander.net wrote:
2010/2/16 Fujii Masao masao.fu...@gmail.com:
On Tue, Feb 16, 2010 at 12:37 AM, Magnus Hagander mag...@hagander.net
wrote:
With the libpq fixes, I get further (more on that fix later, btw), but
now I get stuck in
2010/2/16 Pavel Stehule pavel.steh...@gmail.com:
I think, so these problem have to be identified in compile stage - but
it can be too strict for all (and can slow down production) - it is
reason for plugin.
What do you think about this idea?
How do you identify them? Running function body
On Tue, Feb 16, 2010 at 1:31 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Tom Lane wrote:
We could adopt the historical policy of sending self-notifies
pre-commit, but that doesn't seem tremendously appetizing from the
standpoint of transactional integrity.
But one traditional
David Fetter wrote:
Folks,
Would it be worthwhile to light up some buildfarm animals on OpenVMS?
http://www.openvms.org/stories.php?story=10/02/09/2319162
Sure, go for it.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
2010/2/16 Hitoshi Harada umi.tan...@gmail.com:
2010/2/16 Pavel Stehule pavel.steh...@gmail.com:
I think, so these problem have to be identified in compile stage - but
it can be too strict for all (and can slow down production) - it is
reason for plugin.
What do you think about this idea?
Greg Smith wrote:
If you think through the implications of that far enough, eventually you
start to realize that you really can't even add a feature that requires
an in-place upgrade hack to fix without first having the code that
performs said hack done. Otherwise you're never completely
Fujii Masao escribió:
Hi,
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not initialized (i.e.,
SetTransactionIdLimit()
Jakub Ouhrabka wrote:
You might want to try setting log_autovacuum_min_duration=0 in the
postgresql.conf
Thanks, tried it. There is nothing in the log - the actual
vacuum/analyze commands are not run (as there is no query activity).
I suspect that autovacuum is checking each database if
On Mon, Feb 15, 2010 at 7:51 PM, Jeroen Vermeulen j...@xs4all.nl wrote:
AFAIC a statement could go to re-planning mode if the shortest execution
time for the generic plan takes at least 10x longer than the longest
planning time. That gives us a decent shot at finding statements where
On Mon, Feb 15, 2010 at 7:11 PM, Bruce Momjian br...@momjian.us wrote:
1. Why do we only do bind-level planning for anonymous wire-level queries?
2. I realize we did anonymous-only because that was the only way we had
in the protocol to _signal_ bind-time planning, but didn't we think of
this
Well using parameters will always have a better chance of producing a
better plan but that's not the only factor people consider important.
For a lot of users *predictability* is more important than absolute
performance. If my web server could run 10% faster that might be nice
but if it's
Greg Stark escribió:
On Tue, Feb 16, 2010 at 2:48 AM, Robert Haas robertmh...@gmail.com wrote:
Upon further review, I also notice that this patch seems to have
falsified the EXPLAIN documentation - both the description of the
BUFFERS option and the description of the FORMAT option are no
Jakub Ouhrabka escreveu:
These databases are archive databases, so there is no user activity - no
connected users. But the stats collector generates load - 20-40% of
modern 2.8GHz core all the time.
Did you try to set stats_temp_directory in a RAM based filesystem?
Any clues what does it
David Fetter da...@fetter.org writes:
Would it be worthwhile to light up some buildfarm animals on OpenVMS?
Have we ever even claimed to support VMS? I have no particular desire
to undertake a major new porting effort.
regards, tom lane
--
Sent via pgsql-hackers
On Tue, Feb 16, 2010 at 2:04 PM, Bruce Momjian br...@momjian.us wrote:
The MOVE_* bits go away after a while by vacuum and there is an easy
solution for 9.1 --- vacuum everything in 9.0. Where things really get
hard is when we have to support two page formats or two data formats in
the same
Hello
Server crash on code
postgres=# create or replace function f() returns void as $$#option
dump begin for i in 1..10 loop raise notice '%', i; end loop; return;
end $$ language plpgsql;
server closed the connection unexpectedly
This probably means the server terminated abnormally
Bruce Momjian wrote:
For primary key, there is no enforcement of the primary key, e.g.:
test= CREATE TABLE parent (name TEXT);
CREATE TABLE
test= CREATE TABLE child (age INT) inherits (parent) ;
CREATE TABLE
test= ALTER TABLE parent ADD primary KEY (name);
Joachim Wieland j...@mcknight.de writes:
On Tue, Feb 16, 2010 at 1:31 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Tom Lane wrote:
We could adopt the historical policy of sending self-notifies
pre-commit, but that doesn't seem tremendously appetizing from the
standpoint of
With the following settings
custom_variable_classes = 'auto_explain'
auto_explain.log_min_duration = 0
auto_explain.log_format = 'xml'
auto_explain.log_analyze = on
auto_explain.log_verbose = on
shared_preload_libraries = 'auto_explain'
I am getting regression failures on the
Pavel Stehule pavel.steh...@gmail.com writes:
I don't would to execute function - it is useless because you need
good UI for execution all path. My idea is different. gram.y has
check_sql_expr rutine. This is used for parser checking every static
SQL fragment in plpgsql function. With some
Federico Di Gregorio wrote:
Even if tests and examples code aren't almost never distributed except
in the psycopg2 source package? A couple of other people contributed to
the tests: if you really feel like it is so important I'll contact them
and ask their permission to use the LGPL3 +
Alvaro Herrera alvhe...@commandprompt.com writes:
Greg Stark escribió:
Oops. Well, I would like to know if I'm in the minority and have to
roll this back before I fix that.
My personal opinion is that displaying number of blocks in all EXPLAIN
formats is more consistent.
FWIW, I vote for
Greg Smith wrote:
Federico Di Gregorio wrote:
Even if tests and examples code aren't almost never distributed except
in the psycopg2 source package? A couple of other people contributed to
the tests: if you really feel like it is so important I'll contact them
and ask their permission to
It could be interesting to see how big a porting effort it was ... ?
I'd say go for it and let's see what is involved ...
On Tue, 16 Feb 2010, Tom Lane wrote:
David Fetter da...@fetter.org writes:
Would it be worthwhile to light up some buildfarm animals on OpenVMS?
Have we ever even
2010/2/16 Pavel Stehule pavel.steh...@gmail.com:
2010/2/16 Hitoshi Harada umi.tan...@gmail.com:
2010/2/16 Pavel Stehule pavel.steh...@gmail.com:
I think, so these problem have to be identified in compile stage - but
it can be too strict for all (and can slow down production) - it is
reason
Alvaro Herrera alvhe...@commandprompt.com writes:
Fujii Masao escribió:
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
* We also discussed the idea of having a NOTIFY command that
would work from Primary to Standby.
Just curious, what's a use case for this?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key:
2010/2/16 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
I don't would to execute function - it is useless because you need
good UI for execution all path. My idea is different. gram.y has
check_sql_expr rutine. This is used for parser checking every static
SQL
Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
* Listen / Notify rewrite. This is the only one of the remaining
patches that is not marked as Ready for Committer, but I think it
would be good if someone (probably Tom) at least took a look at it.
I'm not sure if it's
On Tue, Feb 16, 2010 at 08:11:15AM -0500, Andrew Dunstan wrote:
David Fetter wrote:
Folks,
Would it be worthwhile to light up some buildfarm animals on OpenVMS?
http://www.openvms.org/stories.php?story=10/02/09/2319162
Sure, go for it.
cheers
andrew
Here's what I sent them:
On Tue, Feb 16, 2010 at 3:54 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Greg Stark escribió:
Oops. Well, I would like to know if I'm in the minority and have to
roll this back before I fix that.
My personal opinion is that displaying number of
Zdenek Kotala wrote:
Andrew Dunstan p??e v po 08. 02. 2010 v 20:07 -0500:
Our Solaris *moth members seem to have stopped building. Have we lost them?
Hi Andrew,
The answer is not simple. Yes, we lost Solaris 8 and 9 machines which
was reinstalled and now they are used for different
On Feb 16, 2010, at 4:08 AM, Tim Bunce wrote:
Yes, IIRC, 0 == unknown as far as the server is concerned. It just
tells the server to resolve it when it can.
An extra source of puzzlement is that the oid of the 'unknown' type is
705 not 0, and the unknown type isn't discussed in the docs (as
On Tue, Feb 16, 2010 at 09:11:24AM -0800, David E. Wheeler wrote:
An extra source of puzzlement is that the oid of the 'unknown' type is
705 not 0, and the unknown type isn't discussed in the docs (as far as I
could see).
Yes, I noticed that, too. Greg, do you know the answer to that?
My
On Tue, Feb 16, 2010 at 11:22 AM, David Fetter wrote:
* Shell access from several accounts
* Git or cvs client
* Compiler tools
* Perl of a fairly recent vintage
* Outbound http access
I had access to the HP testdrive before they closed it down (the Unix
servers were down in
On 16/02/10 17:11, David E. Wheeler wrote:
On Feb 16, 2010, at 4:08 AM, Tim Bunce wrote:
Wouldn't work unless you'd installed an AUTOLOAD function into each
schema:: package that you wanted to use. (schema-SP::function_name()
could be made to work but that's just too bizzare :)
Maybe
On Feb 16, 2010, at 9:43 AM, Richard Huxton wrote:
Perhaps it would be better to be explicit about what's going on?
SEARCHPATH-function()
SCHEMA('public')-function2()
Or did SP mean Stored Procedure?
Yes.
On a (kind of) related note, it might be worthwhile to mention search_path in
On Tue, Feb 16, 2010 at 12:39:29PM -0500, Rayson Ho wrote:
On Tue, Feb 16, 2010 at 11:22 AM, David Fetter wrote:
* Shell access from several accounts
* Git or cvs client
* Compiler tools
* Perl of a fairly recent vintage
* Outbound http access
I had access to the HP
On 16/02/10 17:51, David E. Wheeler wrote:
On Feb 16, 2010, at 9:43 AM, Richard Huxton wrote:
Perhaps it would be better to be explicit about what's going on?
SEARCHPATH-function()
SCHEMA('public')-function2()
Or did SP mean Stored Procedure?
Yes.
Hmm - might be worth avoiding that in
Richard Huxton wrote:
On 16/02/10 17:51, David E. Wheeler wrote:
On Feb 16, 2010, at 9:43 AM, Richard Huxton wrote:
Perhaps it would be better to be explicit about what's going on?
SEARCHPATH-function()
SCHEMA('public')-function2()
Or did SP mean Stored Procedure?
Yes.
Hmm -
I know this has been discussed several times and it seems the
conclusin was it's impossible if we would like to use existing XQuery
external modules (some are by license reasons and some are by
techinical reasons).
So it seems the only way to support XQuery is, developing our own
XQuery
On Tue, 2010-02-16 at 16:02 +, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
* We also discussed the idea of having a NOTIFY command that
would work from Primary to Standby.
Just curious, what's a use case for this?
If you have some kind of cache
On Tue, 2010-02-16 at 10:38 -0500, Tom Lane wrote:
2. Add an extra lock to serialize writers to the queue, so that messages
are guaranteed to be added to the queue in commit order.
I assume this is a heavyweight lock, correct?
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing
On Tue, Feb 16, 2010 at 12:21:34PM +0100, Boszormenyi Zoltan wrote:
Does FreeBSD/MIPS really return true for isinf(NaN)?
Actually it's a netbsd beta version, so maybe there's a bug in their libc.
But anyway, the patch doesn't seem to hurt, so I committed it.
Michael
--
Michael Meskes
Maybe you should decrease naptime a bit.
That did the trick, thanks!
Yes. There were some changes that needed to be done to autovacuum so
that it didn't read the stats file too often, but I don't recall if I
got around to it.
I looked at the strace output and there are *writes* to the
Jakub Ouhrabka wrote:
Maybe you should decrease naptime a bit.
That did the trick, thanks!
Yes. There were some changes that needed to be done to autovacuum so
that it didn't read the stats file too often, but I don't recall if I
got around to it.
I looked at the strace output and
Michael Meskes írta:
On Tue, Feb 16, 2010 at 12:21:34PM +0100, Boszormenyi Zoltan wrote:
Does FreeBSD/MIPS really return true for isinf(NaN)?
Actually it's a netbsd beta version, so maybe there's a bug in their libc.
I realized my typo after sending my mail. Sorry if I
2010/2/16 Fujii Masao masao.fu...@gmail.com:
On Tue, Feb 16, 2010 at 1:33 AM, Magnus Hagander mag...@hagander.net wrote:
2010/2/15 Tom Lane t...@sss.pgh.pa.us:
Magnus Hagander mag...@hagander.net writes:
I changed your patch to this, because I find it a lot simpler. The
change is in the
On Tue, Feb 16, 2010 at 10:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
2. Add an extra lock to serialize writers to the queue, so that messages
are guaranteed to be added to the queue in commit order. As long as
fwiw, I think you're definitely on the right track. IMO, any scenario
where an
Ideally, autovacuum would only request a new copy of the file if the
one it got was considerably out of date. Obviously a tenth of a
second is not old enough.
I've tried to look at it and found that's already implemented - see
autovac_refresh_stats(). STATS_READ_DELAY which is set to 1s. Am
Jakub Ouhrabka wrote:
Ideally, autovacuum would only request a new copy of the file if the
one it got was considerably out of date. Obviously a tenth of a
second is not old enough.
I've tried to look at it and found that's already implemented - see
autovac_refresh_stats().
_
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469227/direct/01/
-Original Message-
From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-
ow...@postgresql.org] On Behalf Of Rayson Ho
Sent: Tuesday, February 16, 2010 9:39 AM
To: David Fetter
Cc: Andrew Dunstan; PG Hackers
Subject: Re: [HACKERS] OpenVMS?
On Tue, Feb 16, 2010 at 11:22
Greg Stark wrote:
On Mon, Feb 15, 2010 at 7:11 PM, Bruce Momjian br...@momjian.us wrote:
1. Why do we only do bind-level planning for anonymous wire-level queries?
2. I realize we did anonymous-only because that was the only way we had
in the protocol to _signal_ bind-time planning, but
Greg Stark wrote:
On Tue, Feb 16, 2010 at 2:04 PM, Bruce Momjian br...@momjian.us wrote:
The MOVE_* bits go away after a while by vacuum and there is an easy
solution for 9.1 --- vacuum everything in 9.0. ?Where things really get
hard is when we have to support two page formats or two data
Dann Corbit wrote:
PostgreSQL uses fork(), which is not supported on OpenVMS. However,
the techniques used by the WIN32 version of internal_forkexec() in
src/backend/postmaster/postmaster.c give the VMS version a good
starting point.
For PostgreSQL, you will probably want to use
On Tue, Feb 16, 2010 at 2:56 PM, Dann Corbit wrote:
For PostgreSQL, you will probably want to use LIB$SPAWN() as a rough
equivalent to CreateProcess() on Windows
We will need to support running PostgreSQL as a detached process, and
thus it won't have access to the DCL CLI. The implication is
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
Marc G. FournierHub.Org Hosting
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
Well, there is going to be impact on
_
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/
Bruce Momjian wrote:
Bruce Momjian wrote:
Some more _personalized_ copyright noticed have crept into our source
tree:
/src/tutorial/basics.sourceCopyright (c) 1994, Andrew Yu,
University of California
/contrib/intagg/Makefile Copyright (c) 2001 Digital Music Network by
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
That's step one. Step two is community
On Tue, 2010-02-16 at 15:47 -0500, Andrew Chernow wrote:
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their
Applied. Thanks.
---
Bruce Momjian wrote:
Boszormenyi Zoltan wrote:
Ah, I didn't even see that that section needed to be updated. Good
catch. I'd suggest the following wording:
For a commandSELECT/command or
On Tue, 16 Feb 2010, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
Applied.
---
Bruce Momjian wrote:
Peter Eisentraut wrote:
In 8.3, running \c from a file prints something like
You are now connected to database postgres.
In 8.4 it prints
psql (8.4.1)
You are now
Jeff Davis pg...@j-davis.com writes:
On Tue, 2010-02-16 at 10:38 -0500, Tom Lane wrote:
2. Add an extra lock to serialize writers to the queue, so that messages
are guaranteed to be added to the queue in commit order.
I assume this is a heavyweight lock, correct?
Yeah, that seems the easiest
Merlin Moncure mmonc...@gmail.com writes:
On Tue, Feb 16, 2010 at 10:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
2. Add an extra lock to serialize writers to the queue, so that messages
are guaranteed to be added to the queue in commit order. As long as
fwiw, I think you're definitely on the
Applied.
---
Bruce Momjian wrote:
Guy Rouillier wrote:
On 1/6/2010 3:29 PM, Tom Lane wrote:
Guy Rouillierguyr-...@burntmail.com writes:
Oracle states clearly in the SQL Reference manual:
A modifier can
rocr...@gmx.de (Robert Doerfler) writes:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels
scra...@hub.org (Marc G. Fournier) writes:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding
support for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
But adding it in would
I realized my typo after sending my mail. Sorry if I offended anyone
calling NetBSD FreeBSD. :-)
I was trying to stress the *beta* status. Maybe someone into NetBSD might be
interested in reporting this as a bug. At least it behaves different to all
other archs we have.
Michael
--
Michael
2010/2/16 Fujii Masao masao.fu...@gmail.com:
On Tue, Feb 16, 2010 at 7:20 PM, Magnus Hagander mag...@hagander.net wrote:
2010/2/16 Fujii Masao masao.fu...@gmail.com:
On Tue, Feb 16, 2010 at 12:37 AM, Magnus Hagander mag...@hagander.net
wrote:
With the libpq fixes, I get further (more on that
Applied.
---
Bruce Momjian wrote:
I just realized that log_error_verbosity is in the wrong section in
postgresql.conf and in our manual. It is listed under When to log
when in fact it should be in the What to log
Tim Bunce wrote:
On Sun, Feb 14, 2010 at 10:14:28PM -0500, Andrew Dunstan wrote:
Robert Haas wrote:
We're down to 5 patches remaining, and 1 day remaining, so it's time
to try to wrap things up.
* Package namespace and Safe init cleanup for plperl. Andrew Dunstan
is taking care of
On Tue, Feb 16, 2010 at 09:11:24AM -0800, David E. Wheeler wrote:
On Feb 16, 2010, at 4:08 AM, Tim Bunce wrote:
From the docs:
Immediately after the function name, in parenthesis, a comma separated list
of
type names can be given. For example:
'pi()'
On Feb 16, 2010, at 2:06 PM, Tim Bunce wrote:
I assume that type names can be omitted her, too, yes?
No, it seems not. You have to either repeat the type name the right number
of times, or use '...', which simply duplicates the type name for you
behind the scenes. I'll clarify that in the
On Tue, Feb 16, 2010 at 04:42:29PM -0500, Andrew Dunstan wrote:
Tim Bunce wrote:
On Sun, Feb 14, 2010 at 10:14:28PM -0500, Andrew Dunstan wrote:
Robert Haas wrote:
We're down to 5 patches remaining, and 1 day remaining, so it's time
to try to wrap things up.
* Package namespace and Safe
On Feb 16, 2010, at 2:19 PM, Tim Bunce wrote:
It's certainly been an interesting introduction to PostgreSQL development!
Interesting, eh? Look forward to your blog post about the experience. ;-P
Tim.
p.s. One quick heads-up: David Wheeler has reported a possible issue
with Safe 2.21. I
It's certainly been an interesting introduction to PostgreSQL
development!
Hopefully we haven't scared you off - your work is definitely very
much appreciated (and I at least hope to see you back for 9.1)!
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Joachim Wieland j...@mcknight.de writes:
[ listen/notify patch ]
Applied after rather a lot of hacking.
Aside from the issues previously raised, I changed the NOTIFY syntax to
include a comma between channel name and payload. The submitted syntax
with no comma looked odd to me, and it would
Bruce Momjian br...@momjian.us writes:
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
On Feb 16, 2010, at 3:01 PM, Tom Lane wrote:
I think the reason the client-side docs recommend using zero is to avoid
having clients know about the unknown type explicitly (in particular, to
discourage people from hardwiring 705 into their code). AFAIR there's
not a lot of difference in
1 - 100 of 133 matches
Mail list logo
