Robert Haas robertmh...@gmail.com wrote:
The final CommitFest began November 11, 2008. It closed March 25,
2009 (+ 144 days). Beta1 was released April 15, 2009 (+ 21 days).
I'm not entirely clear on what was happening during the 21 days
between the end of the CommitFest and and the
Pavel Stehule pavel.steh...@gmail.com wrote:
this small patch complete MOVE support in plpgsql and equalize
plpgsql
syntax with sql syntax.
Quick correction on the doc changes:
s/similar as for/similar to/
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Paul Matthews p...@netspace.net.au wrote:
Feedback appreciated.
+ /* As x is the larger value, this must be the correct answer.
Also
+ * avoids division by zero. */
+ if( x == 0.0 )
+ return 0.0;
+
+ /* Trivial case. */
+ if( y == 0.0 )
+ return x;
The
Ron Mayer rm...@cheapcomplexdevices.com wrote:
Josh Berkus wrote:
There's some very good reasons for the health of the project to
have specific release dates and stick to them.
Help me understand why?
I don't know how many places are like this, but to get any significant
staff or
I wrote:
But before I spend a lot of time fine-tuning it, I wanted to post
this as a proof-of-concept draft and see if people think it's on the
right track.
I chose to take the lack of response as an indication that nobody who
cares about this thought there was anything seriously wrong
David Fetter da...@fetter.org wrote:
cvs diff if you're on CVS. If you're using git, commit to your
local repository and git-diff.
I tried that. When I just did it at the top level, it ignored the new
file. When I specified the file:
kgri...@kgrittn-desktop:~/pg/pgsql$ cvs diff -c -N
Greg Sabino Mullane g...@turnstep.com wrote:
-
Plan:
Node Type: Index Scan
Scan Direction: Forward
Index Name: pg_class_relname_nsp_index
Relation Name: pg_class
Alias: pg_class
Startup Cost: 0.00
Total Cost: 8.27
Plan Rows: 1
Plan
Peter Eisentraut pete...@gmx.net wrote:
If it's a new file, it's pointless to send a patch anyway.
If people are OK with just sending the new file, that's cool with me.
From the other posts, it appears that I need to have my own copy of
the repository to do it as a patch, or download a tool.
Bruce Momjian br...@momjian.us wrote:
Yep, the bottom line here is that patches get into CVS, but issues
come up related to the patch, and we keep looking for good fixes,
but once the final commit-fest is over, we _have_ to fix these
issues.
If, hypothetically, it might hold up the
Bruce Momjian br...@momjian.us wrote:
The issues are different for every commitfest-beta period, so I have
no idea what to list there, but we do alway have an open issues wiki
that is maintained, at least for the most recent releases.
After a quick search of the wiki, it appears that the
Bruce Momjian br...@momjian.us wrote:
it gets no easier to make the decisions later rather than now. The
delay forces us to make a final decision. We often had months to
make the decision earlier, but didn't.
So you're advocating that we find a way to force more timely
decisions?
+
+ # This is an example of a Linux LSB conforming init script.
+ # See http://refspecs.freestandards.org/ for more information on LSB.
+
+ # Original author: Kevin Grittner
+
+ # $PostgreSQL$
+
+ #
+ # The only edits needed
Greg Smith gsm...@gregsmith.com wrote:
I'm similarly not sure just what the benefits of a LSB compatible
script are here given that several major distributions like
RHEL/Debian have their own thing they're doing and are unlikely to
change.
I don't know about other platforms, but on SuSE
Peter Eisentraut pete...@gmx.net wrote:
While the major distributions support LSB, the major distributions
also have PostgreSQL packages available and so will likely not need
the init script shipped in the source.
My counter-argument to that would be that the SuSE distribution's
version of
Peter Eisentraut pete...@gmx.net wrote:
On mån, 2009-08-31 at 15:17 -0500, Kevin Grittner wrote:
the SuSE distribution's version of PostgreSQL is so out-of-date
that we don't install it. It also doesn't enable debug info or
integer date times.
Fixes and help are welcome, btw.
We're
Robert Haas robertmh...@gmail.com wrote:
I think we should always or never show the view definition, not
sometimes.
+1
And I also agree with Tom's point that we should fix the pager. The
way that it works now is really annoying.
+1
-Kevin
--
Sent via pgsql-hackers mailing list
Peter Eisentraut pete...@gmx.net wrote:
On tis, 2009-09-01 at 12:04 -0500, Kevin Grittner wrote:
I wouldn't expect a packaged SuSE build to cater to all of that;
but it would be nice if they donated their init script to the
PostgreSQL project, so that those of us who have a reason to build
Greg Stark gsst...@mit.edu wrote:
Kevin Grittnerkevin.gritt...@wicourts.gov wrote:
# Copyright (c) 2006 SUSE Linux Products GmbH, Nuernberg, Germany.
# All rights reserved.
and that I would be violating that copyright by copying it to
PostgreSQL. Am I wrong?
The above is just a statement
Andrew Dunstan and...@dunslane.net wrote:
Kevin Grittner wrote:
[SuSE Linux Enterprise Server license]
Novell reserves all rights not expressly granted to You. You may
not:
(2) transfer the Software or Your license rights under this
Agreement, in whole or in part.
here is what's
Greg Stark gsst...@mit.edu wrote:
I don't think we want to cluster on the primary key. I think we just
want to rewrite the table keeping the same physical ordering.
Well if that's what you want to do, couldn't you do something like?:
Lock the table.
Prop all indexes
Pass the heap with two
database.
+ # See http://www.postgresql.org/ for more information.
+ ### END INIT INFO
+
+ # This is an example of a Linux LSB conforming init script.
+ # See http://refspecs.freestandards.org/ for more information on LSB.
+
+ # Original author: Kevin Grittner
+
+ # $PostgreSQL
Robert Haas robertmh...@gmail.com wrote:
It also seems to me logically inconsistent that we would expose this
information via the CREATE TRIGGER interface but not to the trigger
function itself. From within the function, you can compare NEW and
OLD, but you get no visibility into which
Joshua D. Drake j...@commandprompt.com wrote:
/me pokes Robert Haas and Kevin Grittner
I'm honored to be suggested for such a role. I'm happy to do what I
can, but am reluctant to put myself too squarely in any critical path,
as I have responsibility for dealing with some family health
Josh Berkus j...@agliodbs.com wrote:
So I think it would make sense for you guys to do Alpha2.
I'm not really clear on what that means. I'm assuming that part of
the goal is for us to become more intimately familiar with the details
of putting together a release, documenting the process, and
David Fetter da...@fetter.org wrote:
CREATE TRIGGER trig BEFORE UPDATE ON tbl FOR EACH ROW
WHEN (NEW.col IS DISTINCT FROM OLD.col)
EXECUTE PROCEDURE trigger_func();
How much does that buy you versus including this at the start of
trigger_func:
IF (NEW.col IS NOT DISTINCT FROM
Given the desire to defer pinning the type of a literal, for better
support of user defined types, I think the current semantics of all
the conditional expressions:
http://www.postgresql.org/docs/8.4/interactive/functions-conditional.html
are somewhat broken.
As a quick sample of something
Peter Eisentraut pete...@gmx.net wrote:
On Tue, 2009-09-08 at 13:18 -0500, Kevin Grittner wrote:
As a quick sample of something which I believe implements the
correct semantics for COALESCE and NULLIF, see the functions below.
You might want to show before and after, so it's clear what you
Alvaro Herrera alvhe...@commandprompt.com wrote:
Both DB2 and Oracle have an ENFORCE setting for constraints, and a
MySQL blog hinted some time ago that it might be in SQL 201x.
If I remember correctly, Sybase never checks the existing data when
you add a constraint of any type (except for a
Josh Berkus j...@agliodbs.com wrote:
Would this just work on columns on the end, or would it work on the
basis of parsing the CSV header and matching columns?
While the former functionality would be relatively simple, I think
the
latter is what people really want.
It's been a while since
Dann Corbit dcor...@connx.com wrote:
Kevin Grittner
It's been a while since I've had a need for something like this,
but of the copy features not currently available in PostgreSQL,
the two most useful are to read in only some of the defined
columns, and to output to a separate disk file
Robert Haas robertmh...@gmail.com wrote:
There are languages much less obscure than Haskell that support
passing functions as arguments to other functions, such as C.
Or Java, which lets you, for example, pass a Class or Method as an
argument, and includes support for generics.
I see that
Pavel Stehule pavel.steh...@gmail.com wrote:
what is more readable?
select 'i=' || i || ', b=' || b || ', c=' || c ..
or
select format('i=%, b=%, c=%', i, b, c ..)
Seriously, those are about dead even for me. The concatenation
might have a slight edge, particularly since I have the
Alvaro Herrera alvhe...@commandprompt.com wrote:
the format version is a lot better than the || alternative.
Well, if you're trying to tell me what is easier for me to read,
you're probably wrong. I won't presume to try to tell you what you
find easier to read.
I think the main benefit of
Sam Mason s...@samason.me.uk wrote:
On Wed, Sep 09, 2009 at 10:25:34AM -0400, Tom Lane wrote:
Now admittedly there's probably not any major technical obstacle to
making a runtime conversion happen --- it's merely delayed
invocation of the destination type's input function. But I find it
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
I'm only proposing parse-time changes for conditional
expressions -- the CASE predicate and its abbreviations.
No, you are not; you are proposing run-time changes, specifically
the need to coerce unknown
Sam Mason s...@samason.me.uk wrote:
what you you want is full type-inference as it's only that which
will allow you to track back up the layers and assign consistent
types to arbitrary expressions like the above.
Well, obviously that would fix it; I'm not clear on why *only* that
would fix
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
I was thinking of changing what is currently done, for example,
here:
newc-coalescetype = select_common_type(pstate, newargs,
COALESCE, NULL);
Is that so late as you say, or is there a reason
Tom Lane t...@sss.pgh.pa.us wrote:
I'm expecting coerce_type to fail, along the lines of
ERROR: failed to find conversion function from unknown to whatever
OK. After playing with that and reading the code in more depth, I now
see what you've been saying.
[picks up lance and takes aim at
Greg Smith gsm...@gregsmith.com wrote:
Putting on my DBA hat for a minute, the first question I see people
asking is how do I measure how far behind the slaves are?.
Presumably you can get that out of pg_controldata; my first question
is whether that's complete enough information? If not,
Martijn van Oosterhout klep...@svana.org wrote:
FWIW, I find the ability in Slony to configure triggers so they work
or not depending on the replication role to be extremely useful.
Absolutely a major positive feature.
Yeah, as a general rule it doesn't make sense to try to enforce
Scott Mohekey scott.mohe...@telogis.com wrote:
What is the relationship between Timestamp and TimestampTz?
TIMESTAMP WITHOUT TIME ZONE does not identify a moment in time without
first associating it with a time zone. When Daylight Saving Time
ends, the same TIMESTAMP WITHOUT TIME ZONE values
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Kevin Grittner wrote:
IMO, it would be best if the status could be sent via NOTIFY.
To where?
To registered listeners?
I guess I should have worded that as it would be best if a change is
replication status could be signaled
Scott Mohekey scott.mohe...@telogis.com wrote:
I think the issue is that we treat TIMESTAMP WITHOUT TIME ZONE as
TIMESTAMP at GMT. We then convert it to a users local timezone
within application code.
That sounds like an accident waiting to happen. Sure, you can make
it work, but you're
Andrew Gierth and...@tao11.riddles.org.uk wrote:
Kevin == Kevin Grittner kevin.gritt...@wicourts.gov
writes:
Kevin TIMESTAMP WITH TIME ZONE is not completely ANSI-compliant,
Given that the spec requires that 2009-01-31 + interval 1 month =
2009-02-31 (yes, really! see general rule 4
Peter Eisentraut pete...@gmx.net wrote:
The commitfest lists this as the last patch, but there was some
discussion after this. Could you/we clarify what is actually
proposed for inclusion now? I have seen proposals for:
- Linux LSB init script
- Linux non-LSB init script
- SUSE
std pik std...@gmail.com wrote:
How can I get information about the hardware utilization:
This list is for discussing development of the PostgreSQL product.
Please re-post on the novice or admin list. You'll be more likely
to get a useful reply if you give people more information, like
Tom Lane t...@sss.pgh.pa.us wrote:
[ shrug... ] We *have* that property, for sane cases such as
adding and subtracting a fixed number of days.
Adding and subtracting months is very common in business software.
I have seen application bugs related to this many times. I suspect
that such
Andrew Gierth and...@tao11.riddles.org.uk wrote:
(To me, the fact that the spec's idea of 2009-01-31 + 1 month
corresponds to a value that current_date will never be equal to is
a far greater show-stopper.)
You get to pick which way you want to normalize that to the calendar
-- 31 days past
Since our shop seems to use domains more than most, I figured I
should comment on this thread.
Sam Mason s...@samason.me.uk wrote:
On Tue, Sep 15, 2009 at 02:54:18PM +0100, Andrew Gierth wrote:
and the wording from 6.12 implies that that check is still
skipped in the case of NULLs (so that
Peter Eisentraut pete...@gmx.net wrote:
OK, I have a number of comments on this proposal.
Thanks for looking at it.
What does it buy us, in general, and compared to the existing
(non-LSB) script?
A conforming script for use in LSB conforming implementations.
what LSB actually
Josh Berkus j...@agliodbs.com wrote:
a) To date, I have yet to hear a single person bring up an actual
real-life use-case where VACUUM FULL was desireable and REWRITE
would not be.
Would rewrite have handled this?:
http://archives.postgresql.org/pgsql-hackers/2009-09/msg01016.php
-Kevin
Robert Haas robertmh...@gmail.com wrote:
I think this should be in core, not a contrib module.
+1
I also wonder whether we should consider teaching regular VACUUM to
do a little of this every time it's run. Right now, once your table
gets bloated, it stays bloated forever, until you
Emmanuel Cecchet m...@asterdata.com wrote:
I just wonder how many users are using a single psql to manage
multiple server instances of different older versions.
I do that, but I do try to keep all the active versions on my machine,
so that I can use one which exactly matches any of our 100
Peter Eisentraut pete...@gmx.net wrote:
I think it's important to consider what the conforming behavior
really achieves in practice. The INFO section is essential nowadays
for correct functioning on a large portion of distributions. The
exit codes are relatively uninteresting but
Robert Haas robertmh...@gmail.com wrote:
Peter Eisentraut pete...@gmx.net wrote:
On Sun, 2009-09-20 at 22:54 -0400, Robert Haas wrote:
It seems like there is some support for what this patch is trying
to do, but much disagreement about the details of how to get
there. Where do we go from
decibel deci...@decibel.org wrote:
*any* step that improves dealing with table bloat is extremely
welcome, as right now you're basically stuck rebuilding the table.
+1
Although, possibly more irritating than actually rebuilding it is
evaluating borderline bloat situations to determine if
daveg da...@sonic.net wrote:
On Tue, Sep 22, 2009 at 10:27:19AM +0530, Jeevan Chalke wrote:
It seems that Oracle reads formatting string from right-to-left.
Here are few results:
('number','format') == Oracle PG
('34,50','999,99') ==
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
daveg da...@sonic.net wrote:
On Tue, Sep 22, 2009 at 10:27:19AM +0530, Jeevan Chalke wrote:
It seems that Oracle reads formatting string from right-to-left.
It seems worse to to give a wrong answer
Joshua D. Drake j...@commandprompt.com wrote:
On Wed, 2009-09-30 at 19:08 -0500, Kevin Grittner wrote:
I don't currently have access to an Oracle database
Just download developer edition?
[quick google search]
Looks like that would do it. Thanks.
-Kevin
--
Sent via pgsql-hackers
Jaime Casanova jcasa...@systemguards.com.ec wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Although come to think of it ... is there any reason besides sheer
conservatism to not make the default listen_addresses value '*'?
just my 2 cents. but i always wondered about the existence of
Simon Riggs si...@2ndquadrant.com wrote:
It would be more useful to think of this as look for huge chunks of
space and fill them rather than start at beginning, since space
won't always be right at start.
Either I misunderstand you or I disagree. If there's a huge chunk of
space near the
Tom Lane t...@sss.pgh.pa.us wrote:
Simon Riggs si...@2ndquadrant.com writes:
Yes, as Tom points out, this must be done with bias away from the
very end of the table.
I meant that we should start from the beginning of large spaces and
that we shouldn't assume that all space worth filling is
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Kevin Grittner wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
So for example we might try resetting the search to the start of
the
relation with probability 0.01.
If I understand the heuristic you propose, and my math skill
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
0.99 percent chance to continue the sweep
Make that a 99% chance, or a 0.99 chance (in case the typo was not
apparent).
Am I saying something stupid here?
Well, besides that line?
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql
Robert Haas robertmh...@gmail.com wrote:
The elephant in the room here is that if the relation is a million
pages of which 1-100,000 and 1,000,000 are in use, no amount of bias
is going to help us truncate the relation unless every tuple on page
1,000,000 gets updated or deleted.
Perhaps
Tom Lane t...@sss.pgh.pa.us wrote:
(Hm, so we might want to make the probability depend on
max_connections?)
Without doing rigorous math on it, I'd guess that to prevent
contention among n connections you'd want the probably of resetting
the sweep to be about 1 / (n * 2). That would mean
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
I think it would make sense to just start using this once you get
into the last half or quarter of the free pages. If you go with the
last quarter, then you might want to use a higher probability than I
suggested above, although that would
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
[pages with free space or total pages in relation?]
It's going to be the latter --- we do not know, and are *not* going
to invest the cycles to find out, how many pages have a useful
amount of free space
Robert Haas robertmh...@gmail.com wrote:
let's let the default, global default ACL contain the hard-wired
privileges, instead of making them hardwired.
+1
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Andrew Dunstan and...@dunslane.net wrote:
We have this para in the CREATE TABLE docs, commented out
Surely we should either include it or remove it.
+1
If it's deleted, it'll still be in CVS history if someone wants it
-Kevin
--
Sent via pgsql-hackers mailing list
Stephen Frost sfr...@snowman.net wrote:
Do we have a patch which implements the necessary mechanics to
replace RULEs, even for the specific situations you list? Until
then, I don't think there's much to discuss.
I thought that until we had discussion and consensus it was premature
to start
Robert Haas robertmh...@gmail.com wrote:
It seems quite odd to me that when COPY succeeds but there are
errors, the transaction commits. The only indication that some of
my data didn't end up in the table is that the output says COPY n
where n is less than the total number of rows I
Tom Lane t...@sss.pgh.pa.us wrote:
Hmm, if we were willing to break COPY into multiple *top level*
transactions, that would avoid my concern about XID wraparound.
The issue here is that if the COPY does eventually fail (and there
will always be failure conditions, eg out of disk space), then
Peter Eisentraut pete...@gmx.net wrote:
I think the setting ought be called linestyle unicode (instead of
utf8), since the same setting would presumably work in case we ever
implement UTF-16 support on the client side.
Yeah, anytime one gets sloppy with the distinction between a character
Robert Haas robertmh...@gmail.com wrote:
I sometimes want to know what the planner thinks the cost of some
plan other than the one actually selected would be.
Another DBMS I used for years had a way to turn on an *extremely*
verbose mode for their planner; it showed everything it considered
Tom Lane t...@sss.pgh.pa.us wrote:
5. Now commit in the second session. First session resumes and
prints
f1 | f2 | f3 | f4
+++-
1 | 1 | 1 | 111
1 | 1 | 1 | 112
2 | 42 | 2 | 113
2 | 42 | 2 | 114
2 | 42 | 2 | 113
2 | 42 | 2 | 114
(6 rows)
Of
Dave Page dp...@pgadmin.org wrote:
I said up front this was a box-ticking exercise for these folks,
Can they check the box if the provided clients include password
strength checking? I'm just wondering if we're going at this the hard
way, if that really is the main goal.
From the point of
David Fetter da...@fetter.org wrote:
On Wed, Oct 14, 2009 at 04:51:03PM -0400, Tom Lane wrote:
Rod Taylor rod.tay...@gmail.com writes:
I tried making a functional index based on an expression
containing the 2 argument regexp_matches() function. Is there a
reason why this function is not
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
if the login password is sent over a non-encrypted stream, md5sum
or not, can't someone use it to log in if they're generating their
own stream to connect?
If they see the md5'd password in a CREATE USER
Dave Page dp...@pgadmin.org wrote:
No. Any checks at the client are worthless, as they can be bypassed
by 10 minutes worth of simple coding in any of a dozen or more
languages.
Well, sure, but we're talking about a client going out of their way to
wrestle the point of the gun toward their
Dave Page dp...@pgadmin.org wrote:
On Wed, Oct 14, 2009 at 10:51 PM, Kevin Grittner
bigger problems, like that slip of paper in their desk drawer with
the password written on it.
See my previous comment about dates. Check-box items aside, I have
absolutely no desire to try to give
Dimitri Fontaine dfonta...@hi-media.com wrote:
It's pretty often the case (IME) that calling a trigger is the only
point in the session where you fire plpgsql, and that's a visible
cost.
Wouldn't a connection pool solve this?
-Kevin
--
Sent via pgsql-hackers mailing list
David Fetter da...@fetter.org wrote:
Could you point to a reference for this? It could help the rest of
us
see what you're aiming for even better :)
Sybase Adaptive Server Enterprise (ASE)
clientapplname varchar(30) column in sysprocesses table:
Robert Haas robertmh...@gmail.com wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
I think Pavel's entire line of argument is utter nonsense.
+1. I can't even understand why we're still arguing about this.
Agreed. One premise of the whole concept was don't even think of
using it for
David E. Wheeler da...@kineticode.com wrote:
I'd be in favor of a GUC that I could turn on to throw an error
when there's an ambiguity.
I would consider hiding one definition with another very bad form, so
I would prefer to have plpgsql throw an error when that happens. I
don't particularly
Tom Lane t...@sss.pgh.pa.us wrote:
(a) Nobody but me is afraid of the consequences of treating this as
a GUC.
Well, it seems dangerous to me, but I'm confident we can cover this
within our shop, so I'm reluctant to take a position on it. I guess
the main question is whether we want to allow
Robert Haas robertmh...@gmail.com wrote:
I've been wondering if it might make sense to have a
random_page_cost and seq_page_cost setting for each TABLESPACE,
to compensate for the fact that different media might be faster or
slower, and a percent-cached setting for each table over top of
Jeff Davis pg...@j-davis.com wrote:
what kind of scenario
would involve a stable 90% cache hit ratio for a table?
I'd bet accounts receivable applications often hit that.
(Most payments on recent billings; a sprinkling on older ones.)
I'm sure there are others.
-Kevin
--
Sent via
Greg Smith gsm...@gregsmith.com wrote:
The unfortunate reality of accounts receivable is that reports run
to list people who owe one money happen much more often than posting
payments into the system does.
How often do you have to print a list of past due accounts? I've
generally seen that
Andrew Dunstan and...@dunslane.net wrote:
What I think we might sensibly do is to eat the leading BOM of an
SQL file iff the client encoding is UTF8, and otherwise treat it as
just bytes in whatever the encoding is.
Only at the beginning of the file or stream? What happens when people
Tom Lane t...@sss.pgh.pa.us wrote:
if your software is written to depend on the appname being set a
particular way
then you're not using for its intended purpose, I should think. Since
any client can set this to whatever they want, having the application
name as a default, rather than NULL
David Fetter da...@fetter.org wrote:
I'd like to see about removing the following GUCs:
sql_inheritance (should be on)
I'd rather see that stay, so that I can make sure it's off. That
said, we have other ways to enforce shop policy on this, if need be.
track_counts (should be on)
I
Magnus Hagander mag...@hagander.net wrote:
For java, it doesn't even go through libpq, so it wouldn't be set
for it. And I'd expect the JDBC driver to set it based on Something
Reasonable (TM) that it can get the information about. After all,
this thing was listed in the JDBC spec somebody
Tom Lane t...@sss.pgh.pa.us wrote:
[ scratches head... ] I thought the JDBC spec already said exactly
how one would set this. Why would we go to significant effort to
make it behave contrary to spec?
We certainly should allow it to be set as specified in the spec. The
only question is
Dave Page dp...@pgadmin.org wrote:
Robert Haas robertmh...@gmail.com wrote:
I also like PGAPPNAME better, for the same reasons as Tom.
:-). Have to admit, I've mistyped it a few times too.
Well, it would seem we have consensus on that. :-)
I don't feel that the Java default issue
Greg Stark gsst...@mit.edu wrote:
There is another use case which perhaps needs to be addressed: if
the user has some queries which are very latency sensitive and
others which are not latency sensitive.
Yes. Some products allow you to create a named cache and bind
particular objects to it.
Tom Lane t...@sss.pgh.pa.us wrote:
Any change here is *not* a bug fix, it is a change of clearly
documented and not-obviously-unreasonable behavior. We have to take
seriously the likelihood that it will break existing code.
Perhaps plpgsql could support tests of SQLSTATE, and recognize
David Fetter da...@fetter.org wrote:
One of the things the security community has learned is that the
only way it's even possible to get an information leak rate of zero
is to have a system which does nothing at all. It's a fact we need
to bear in mind when addressing this or any other
Robert Haas robertmh...@gmail.com wrote:
I realize that the current file format is an old and familiar
friend; it is for me, too. But I think it's standing in the way of
progress. Being able to type a SQL command to update postgresql.conf
would be more substantially convenient than logging
Jonah H. Harris jonah.har...@gmail.com wrote:
Joshua D. Drake j...@commandprompt.comwrote:
This reply is wholly inappropriate for a Pg list. We are here to
help people. If you have a consultancy, please feel free to list
that but any discussion of rates is just plain rude. Please use
better
601 - 700 of 3976 matches
Mail list logo
