On Thu, Jul 31, 2008 at 02:46:29PM +0900, Hitoshi Harada wrote:
> 2008/7/31 David Fetter <[EMAIL PROTECTED]>:
> > On Thu, Jul 31, 2008 at 02:12:26PM +0900, Hitoshi Harada wrote:
> >> 2008/7/29 David Fetter <[EMAIL PROTECTED]>:
> >> > On Mon, Jul 28, 2008 at 07:25:55PM +0900, H.Harada wrote:
> >> >>
2008/7/31 David Fetter <[EMAIL PROTECTED]>:
> On Thu, Jul 31, 2008 at 02:12:26PM +0900, Hitoshi Harada wrote:
>> 2008/7/29 David Fetter <[EMAIL PROTECTED]>:
>> > On Mon, Jul 28, 2008 at 07:25:55PM +0900, H.Harada wrote:
>> >> I happily announce that the first design of window function was
>> >> fin
On Thu, Jul 31, 2008 at 02:12:26PM +0900, Hitoshi Harada wrote:
> 2008/7/29 David Fetter <[EMAIL PROTECTED]>:
> > On Mon, Jul 28, 2008 at 07:25:55PM +0900, H.Harada wrote:
> >> I happily announce that the first design of window function was
> >> finished and the patch against HEAD is released onlin
2008/7/29 David Fetter <[EMAIL PROTECTED]>:
> On Mon, Jul 28, 2008 at 07:25:55PM +0900, H.Harada wrote:
>> I happily announce that the first design of window function was
>> finished and the patch against HEAD is released online. See
>> http://umitanuki.net/pgsql/wfv03/design.html
>
> I've put up a
Hi all,
There is an opportunity to get remote access to a 16 CPU Itanium (or
possibly bigger) system at HP. If anyone is interested Bob Gobeille
at HP (cc'ed) will do what he can to get remote access. Maybe some
scalability work or something? :) We don't have many details at the
moment, but Bob
"Henry B. Hotz" <[EMAIL PROTECTED]> writes:
> What's the time frame for 8.4?
http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Development_Plan
Executive summary: new-feature patches had better be submitted before
1 November.
> I'm making no promises, but what would people think of a hostgss hba
* Henry B. Hotz ([EMAIL PROTECTED]) wrote:
> I'm making no promises, but what would people think of a hostgss hba
> option?
As described, sounds like a win to me. It'd be very nice to be able to
just use GSSAPI encryption on the link. That, combined w/ Magnus' work
on username/princ mappings,
What's the time frame for 8.4?
I'm making no promises, but what would people think of a hostgss hba
option?
Using it would imply the gssapi/sspi authentication option. It would
be mutually exclusive of the ssl link-encryption option. It would
support strong encryption of the whole conne
daveg <[EMAIL PROTECTED]> writes:
> On Wed, Jul 30, 2008 at 04:45:47PM +0900, ITAGAKI Takahiro wrote:
>> Here is a patch to copy column storage parameters and reloptions on
>> CREATE TABLE LIKE, which I proposed at:
> I'd like to have the ability to copy these parameters, but not to have it
> be a
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Another issue is, some node types are not supported in outfuncs.c.
> WARNING: could not dump unrecognized node type: 911
Yeah. I think there's an unofficial policy for post-analysis parse
trees that we don't bother writing outfuncs for utility-statement
> Isn't the post-parse-analysis tree far more interesting? There's
> already debug support for printing that.
It's interesting too. But I think compraring raw parse tree and
post-parse-analysis tree is sometimes usefull to understand the source
code.
> Of course, you can call pprint() from anypl
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> Unless you're going to allow them to create new C functions, I'm not
>> clear on how much they're going to be able to change the semantics.
> Well there's plenty that can be done just using text or bytea as
> rep
Tom Lane wrote:
> If you're not clear on why CREATE TYPE in the hands of a bad guy is
> dangerous, here are a couple of reasons:
>
> * By specifying type representation details (len/byval/align) that are
> different from what the type's functions expect, you could trivially
> crash the backend, a
"Tom Lane" <[EMAIL PROTECTED]> writes:
>> As a consequence we could perhaps aim to make creating new types safe rather
>> than just deal with the fact that it's not safe currently? It would be nice
>> if
>> non-superusers could create types which used an existing set of input/output
>> functions
Gregory Stark <[EMAIL PROTECTED]> writes:
> I know when I was first starting out it was a big source of frustration that
> you have to get those arguments right.. Until I figured out what they all
> meant and how to use them I was constantly crashing the server.
> It seems to me we should be able
"Tom Lane" <[EMAIL PROTECTED]> writes:
> If you're not clear on why CREATE TYPE in the hands of a bad guy is
> dangerous, here are a couple of reasons:
>
> * By specifying type representation details (len/byval/align) that are
> different from what the type's functions expect, you could trivially
On Wed, Jul 30, 2008 at 04:45:47PM +0900, ITAGAKI Takahiro wrote:
> Here is a patch to copy column storage parameters and reloptions on
> CREATE TABLE LIKE, which I proposed at:
> [HACKERS] Uncopied parameters on CREATE TABLE LIKE
> http://archives.postgresql.org/message-id/[EMAIL PROTECTED]
>
On Jul 30, 2008, at 12:58, Tom Lane wrote:
Well, from a user's point of view, they're pretty much just strings
But they're a very restricted set of strings; I can't see that there's
any general-purpose use for allowing them as the source or destination
of I/O conversions.
*shrug* Okay, no bi
"David E. Wheeler" <[EMAIL PROTECTED]> writes:
> On Jul 30, 2008, at 10:34, Tom Lane wrote:
>> UUID and so on aren't considered part of the string category, and
>> shouldn't be IMHO ... any type that has semantics significantly
>> different from "arbitrary string of text" doesn't belong.
> Yes, th
"David E. Wheeler" <[EMAIL PROTECTED]> writes:
> On Jul 30, 2008, at 11:09, Tom Lane wrote:
>>> What about enums?
>>
>> Er, what about them? I don't see that they enter into this at all.
> Well, from a user's point of view, they're pretty much just strings
But they're a very restricted set of
Currently, you're allowed to create a new base type if you own the I/O
functions for it. That effectively restricts the command to superusers
anyway, since there's presently no way for a non-superuser to create
a function that would have the required signature. However that's a
fairly indirect pr
On Jul 30, 2008, at 11:09, Tom Lane wrote:
What about enums?
Er, what about them? I don't see that they enter into this at all.
Well, from a user's point of view, they're pretty much just strings…
Best,
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Jul 30, 2008, at 10:42, David E. Wheeler wrote:
I've committed changes along this line. Please look at CVS HEAD and
re-evaluate which alias functions/operators you still really need.
Okay, I'll hunt down some tuits today to hack on that.
The ones you removed all seem to be fine. I'll hav
"David E. Wheeler" <[EMAIL PROTECTED]> writes:
> On Jul 30, 2008, at 10:34, Tom Lane wrote:
>> The behavior that's hard-wired into parse_coerce.c at the moment
>> is that only text, varchar, bpchar can be sources or targets of
>> I/O conversions. While opening it up to citext sounds reasonable,
>>
>>> Tom Lane <[EMAIL PROTECTED]> wrote:
> and you have to remember that *any* domain created over a string
type
> will also be considered to be of string category.
> find_coercion_pathway
> is looking at types that it's already smashed to base types, so
> actually you can get an I/O conversion
On Jul 30, 2008, at 10:34, Tom Lane wrote:
[ move preferred-type info into the system catalogs ]
I've committed changes along this line. Please look at CVS HEAD and
re-evaluate which alias functions/operators you still really need.
Okay, I'll hunt down some tuits today to hack on that.
UU
"David E. Wheeler" <[EMAIL PROTECTED]> writes:
> On Jul 29, 2008, at 16:45, Tom Lane wrote:
>> [ move preferred-type info into the system catalogs ]
I've committed changes along this line. Please look at CVS HEAD and
re-evaluate which alias functions/operators you still really need.
>>> Nice! Do
Heikki Linnakangas wrote:
Andrew Dunstan wrote:
Greg Smith wrote:
On Wed, 23 Jul 2008, Kevin Grittner wrote:
I've been working on an improved archive_command shell script that I
expect to submit for comments and potential inclusion in the
documentation as a better base for other people to bu
2008/7/30 Hannu Krosing <[EMAIL PROTECTED]>:
> On Wed, 2008-07-30 at 08:40 +0200, Pavel Stehule wrote:
>> Hello
>>
>> 2008/7/30 Hannu Krosing <[EMAIL PROTECTED]>:
>> > On Wed, 2008-07-30 at 07:29 +0200, Pavel Stehule wrote:
>> >> 2008/7/29 Hannu Krosing <[EMAIL PROTECTED]>:
>> >> > On Thu, 2008-07-
Hello Tom,
On Wed, Jul 30, 2008 at 7:50 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Dunno, I forget what the conclusion was about implicit casting for the
> unsigned types in your proposal. Have you experimented with seeing
> whether, eg, UNION'ing an unsigned with some signed-integer value
> behav
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Very often I find it is useful to print raw parse trees for debugging
> and/or understanding PostgreSQL internals and I personally modify
> pg_parse_query() to accomplish it. If this is common among developers,
> I would like to post small patches. Opinion
"Ryan Bradetich" <[EMAIL PROTECTED]> writes:
> On Tue, Jul 29, 2008 at 2:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Yeah, that's the point of the proposal. I think the issue has come up
>> once or twice before, too, else I'd not be so interested in a general
>> solution. (digs in archives ...
Alvaro Herrera wrote:
Today, using --inputdir in pg_regress does not work for any other value
than something that resolves to cwd, since it will write a file to
"./sql", but try to read the same file from "/sql".
Maybe I'm missing something, but I don't see any reason why this is a
scenario
On Wed, 2008-07-30 at 08:40 +0200, Pavel Stehule wrote:
> Hello
>
> 2008/7/30 Hannu Krosing <[EMAIL PROTECTED]>:
> > On Wed, 2008-07-30 at 07:29 +0200, Pavel Stehule wrote:
> >> 2008/7/29 Hannu Krosing <[EMAIL PROTECTED]>:
> >> > On Thu, 2008-07-17 at 19:13 -0400, Tom Lane wrote:
> >> >> I've been
Gregory Stark <[EMAIL PROTECTED]> writes:
> I had a different thought when you posted the original prompt earlier. Instead
> of a static list of type categories we could re-use type oids. So if you
> belong to a type category you store the oid of the preferred type of that
> category in typcategory
Jorgen Austvik - Sun Norway wrote:
> Alvaro Herrera wrote:
>> I think this breaks VPATH builds in both letter and spirit.
>
> Letter:
>
> 8<---8<---8<---8<---8<---8<---
> bash-3.2$ ggrep -R "\-\-inputdir" *
> src/test/regress
"Tom Lane" <[EMAIL PROTECTED]> writes:
> So this can fairly obviously be replaced by two new pg_type columns,
> say "typcategory" and "typpreferred", where the latter is a bool.
> Since the list of categories is pretty short and there's no obvious
> reason to extend it a lot, I propose that we jus
Stephen R. van den Berg wrote:
>A.M. wrote:
>>Anyway, what does "The driver beats libpq in speed by about 62%" mean?
>I.e. speed comparison is 762/483 = 1.63 -> 63% faster.
After some tuning on the libpq side, I can say that:
If libpq is called using a cursor and fetches in 64 row chunks the spe
Alvaro Herrera wrote:
Jorgen Austvik - Sun Norway wrote:
The attached patch makes pg_regress write converted files to
/sql and /expected, which is one way to make it read
and write to the same directory. Tested on Solaris x86 with pgsql "make
check" and standalone.
I think this breaks VP
Very often I find it is useful to print raw parse trees for debugging
and/or understanding PostgreSQL internals and I personally modify
pg_parse_query() to accomplish it. If this is common among developers,
I would like to post small patches. Opinion?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
--
Sent v
Markus Wanner 写道:
Hello Leiyonghua,
leiyonghua wrote:
at node2, and the psql command is hung up,
NOTICE: Applying for membership in the communication group...
NOTICE: Successfully joined the replication group. Now recovering
schema...
I've just tested the very same here with ensemble, and c
Hi,
That's now changed in today's snapshot of Postgres-R: the postmaster no
longer uses imessages (and thus shared memory) to communicate with the
replication manager. Instead the manager signals the postmaster using a
newish PMSIGNAL for requesting new helper backends. It now only requests
o
Hello Leiyonghua,
leiyonghua wrote:
at node2, and the psql command is hung up,
NOTICE: Applying for membership in the communication group...
NOTICE: Successfully joined the replication group. Now recovering schema...
I've just tested the very same here with ensemble, and could reproduce
the
At 2008-07-29 15:42:27 +0530, [EMAIL PROTECTED] wrote:
>
> OK, I have a mostly working pg_get_functiondef now, and some
> questions about the remaining pieces:
While I look for answers to those questions, here's the patch as it
stands now, in case anyone feels like reading through it.
-- ams
diff
Here is a patch to copy column storage parameters and reloptions on
CREATE TABLE LIKE, which I proposed at:
[HACKERS] Uncopied parameters on CREATE TABLE LIKE
http://archives.postgresql.org/message-id/[EMAIL PROTECTED]
Column storage parameters (by ALTER COLUMN SET STORAGE) and table
storage p
Tom,
On Tue, Jul 29, 2008 at 2:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Yeah, that's the point of the proposal. I think the issue has come up
> once or twice before, too, else I'd not be so interested in a general
> solution. (digs in archives ... there was some discussion of this
> in conne
46 matches
Mail list logo
