On Wed, Oct 16, 2002 at 02:08:21PM -0400, Curtis Faith wrote:
2) Including the pros and cons of the feature/implementation and how close
the group is to deciding whether something would be worth doing. - I can
also do this.
The pros and cons of many such features have been discussed over
Bruce Momjian writes:
Peter Eisentraut wrote:
Bruce Momjian writes:
COPY table TO STDOUT WITH BINARY OIDS;
Shouldn't the binary, being an adjective, be attached to something?
Uh, it is attached to WITH?
Attached to a noun phrase, like mode or output. Note that all the
Neil Conway [EMAIL PROTECTED] writes:
Well, I'm not happy with defining _GNU_SOURCE, but I don't agree that
just saying it's a Perl problem is a good answer. That may well be
the case, but it doesn't change the fact that a lot of people are
running 5.8.0, and will probably continue to do so
I have been looking forward to schemas (namespaces) for sometime.
I had not been able to decipher the schema symantics necessary for a
default schema, until I hacked the source a bit.
Now I know that the rules to get a default schema using
db_user_namespace = true
search_path = '$user,public'
Carl Anderson [EMAIL PROTECTED] writes:
this use of @ in the default schema is a bit counter intuitive
so I offer the following patch against CVS
Hmm, this seems like a wart, but then the db_user_namespace feature
is an acknowledged wart already.
I think I'd be willing to hold still for this
Tom Lane wrote:
Carl Anderson [EMAIL PROTECTED] writes:
this use of @ in the default schema is a bit counter intuitive
so I offer the following patch against CVS
Hmm, this seems like a wart, but then the db_user_namespace feature
is an acknowledged wart already.
I think I'd be willing
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
It looks like NAME comparison uses strcmp (actually strncmp). So it'll
be numeric byte-code order.
There's no particular reason we couldn't make that be strcoll instead,
I suppose, except perhaps speed.
But
Gavin Sherry wrote:
On Wed, 16 Oct 2002, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Right now we assume \XXX is octal. We could support \x as hex because
\x isn't any special backslash character. However, no one has ever
asked for this. Does anyone else think this
Lee Kindness wrote:
Bruce Momjian writes:
Peter Eisentraut wrote:
Bruce Momjian writes:
COPY table TO STDOUT WITH BINARY OIDS;
Shouldn't the binary, being an adjective, be attached to something?
Uh, it is attached to WITH?
Attached to a noun phrase, like mode or
Tom Lane writes:
I'm confused; are you saying that NAME's sort behavior is good as-is?
If not, what would you have it do differently?
What I am primarily saying is that ordering the rule execution order
alphabetically is not a really good solution. Consequently, I would not
go out of my way
Lee Kindness writes:
Are you serious? You'd like to mess up the COPY syntax even further
for a purely grammatical reason!
We already messed up the COPY syntax in this release to achieve better
user friendliness. I do not think it's unreasonable to review this goal
from a variety of angles.
Neil Conway writes:
gcc -O2 -g -fpic -I. -I/usr/lib/perl/5.8.0/CORE -I../../../src/include -c -o
plperl.o plperl.c -MMD
In file included from /usr/lib/perl/5.8.0/CORE/op.h:480,
from /usr/lib/perl/5.8.0/CORE/perl.h:2209,
from plperl.c:61:
Peter Eisentraut wrote:
Tom Lane writes:
I'm confused; are you saying that NAME's sort behavior is good as-is?
If not, what would you have it do differently?
What I am primarily saying is that ordering the rule execution order
alphabetically is not a really good solution. Consequently,
Works here:
test= select 5.3::float;
float8
5.3
(1 row)
---
Teodor Sigaev wrote:
wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
wow=# select
I am cleaning up /contrib by adding autocommit = 'on' and making it
more consistent. Should I be adding this too:
-- Adjust this setting to control where the objects get created.
SET search_path = public;
and doing all object creation in one transaction, like /contrib/cube
does?
On Thu, 2002-10-17 at 23:34, Teodor Sigaev wrote:
wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
Could it be something with locales ?
Try:
select 5,3::float;
-
Hannu
---(end of broadcast)---
TIP 5: Have you
Peter Eisentraut [EMAIL PROTECTED] writes:
Can you post some snippets from the relevant code sections? Following one
of the links that were posted I gathered that this is related to
crypt_r(), whose prototype is not exposed on my system unless you use
_GNU_SOURCE. But I don't see any
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I am cleaning up /contrib by adding autocommit = 'on' and making it
more consistent. Should I be adding this too:
-- Adjust this setting to control where the objects get created.
SET search_path = public;
Yes, that
Tom Lane wrote:
I think this is a consequence of the changes made a little while back
(by Peter IIRC?) in locale handling. It used to be that we deliberately
did *not* allow any LC_ setting except LC_MESSAGES to actually take
effect globally in the backend, and this sort of problem is exactly
Hannu Krosing [EMAIL PROTECTED] writes:
On Thu, 2002-10-17 at 23:34, Teodor Sigaev wrote:
wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
Could it be something with locales ?
Oooh, bingo! On HPUX:
regression=# select 5.3::float;
float8
5.3
(1 row)
regression=#
Bruce Momjian [EMAIL PROTECTED] writes:
I am cleaning up /contrib by adding autocommit = 'on' and making it
more consistent. Should I be adding this too:
-- Adjust this setting to control where the objects get created.
SET search_path = public;
Yes, that would be a good idea.
Bruce Momjian [EMAIL PROTECTED] writes:
I dislike double-testing the username in schema areas but not other
places. Seems if we do it, we should do it consistently for all
username references, or not at all.
What other places do we have an explicit dependence on the username?
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I dislike double-testing the username in schema areas but not other
places. Seems if we do it, we should do it consistently for all
username references, or not at all.
What other places do we have an explicit dependence on the
Peter Eisentraut [EMAIL PROTECTED] writes:
Well, I am the first to agree that the current syntax is not well
designed, but I must admit that I don't quite see what benefit simply
adding TABLE would have.
I think the idea was that COPY TABLE ... could have a new clean syntax
without the warts
On Wed, 16 Oct 2002, Bruce Momjian wrote:
It may be optional some day, most likely for Win32 at first, but we see
little value to it on most other platforms; of course, we may be wrong.
I am also not sure if it is a big win on Apache either; I think the
jury is still out on that one, hence
Bruce Momjian [EMAIL PROTECTED] writes:
Let me add one more thing on this thread. This is one email in a long
list of Oh, gee, you aren't using that wizz-bang new
sync/thread/aio/raid/raw feature discussion where someone shows up and
wants to know why. Does anyone know how to address these,
On Thu, 17 Oct 2002, Justin Clift wrote:
Thomas Swan wrote:
Justin Clift wrote:
snip
Ok. Wonder if it's worth someone creating a PostgreSQL Powertools
type of package, that includes in one download all of these nifty
tools (pg_autotune, oid2name, etc) that would be beneficial to
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
I'm confused; are you saying that NAME's sort behavior is good as-is?
If not, what would you have it do differently?
What I am primarily saying is that ordering the rule execution order
alphabetically is not a really good solution.
I have made the changes to pg_dump and verified that (a) it reads old
files, (b) it handles 8 byte offsets, and (c) it dumps seems to restore
(at least to /dev/null).
I don't have a lot of options for testing it - should I just apply the
changes and wait for the problems, or can someone
On Wed, 16 Oct 2002, Anuradha Ratnaweera wrote:
On Wed, Oct 16, 2002 at 01:25:23AM -0400, Bruce Momjian wrote:
Anuradha Ratnaweera wrote:
... what I want to know is whether multithreading is likely to get
into in postgresql, say somewhere in 8.x, or even in 9.x?
It may be optional
30 matches
Mail list logo
