Hello all,
Here is the first pass at the unsigned data type I have been working on.
I am planning on adding these to the September 2008 commitfest wiki page.
The unsigned data type is not targeted for core, but for the uint PgFoundry
project.
The uint.c.gz file is the main source file for the
2008/8/14 Hannu Krosing [EMAIL PROTECTED]:
On Thu, 2008-08-14 at 11:56 +0200, Pavel Stehule wrote:
Hello
I propose enhance current syntax that allows to specify label for any
function parameter:
fcename(expr [as label], ...)
fcename(colname, ...)
also fcename(localvar, ...) if called
2008/8/15 Tom Lane [EMAIL PROTECTED]:
Hannu Krosing [EMAIL PROTECTED] writes:
How is this supposed to interact with argument names ?
Yeah, the real problem with this proposal is that it conscripts a syntax
that we'll probably want to use in the future for argument-name-based
parameter
Thanks for the tip.
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
su pgsql -c '/usr/local/pgsql/bin/postmaster -d 5 -p 5432 -S -o -e -F
-D
I think that you use to much new pg_dump. I'm not sure but my expectation is
that latest pg_dump version does not support too old PG. The problem there could
be network protocol. Currently only version 3 and 2 is supported. I recommend
you to jump to 7.x (7.2) first and use 7.2 pg_dump and
On Fri, Aug 15, 2008 at 9:54 AM, alexander lunyov [EMAIL PROTECTED] wrote:
Thanks for the tip.
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
Hi,
I would like to use one of the XML rendering functions like
table_to_xml_and_xmlschema OR table_to_xml and render the output via XSL,
preferably in one query.
I've searched the mailing lists,site, docs and Google -- to no avail. Also,
I see that xslt_process (from xml2) will be deprecated
Guillaume Smet wrote:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
Do you have something like tcpip_socket in your postgresql.conf (I
don't know if
alexander lunyov wrote:
Guillaume Smet wrote:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
Maybe you should just dump schema and data separately
Andreas Pflug wrote:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
Maybe you should just dump schema and data separately with your old
pg_dump
On Fri, Aug 15, 2008 at 11:42 AM, alexander lunyov [EMAIL PROTECTED] wrote:
i didn't find anything like postgresql.conf on old server. Right now i'm
tried to start 6.5.3 on windows (downloaded binary from ftp archive on
postgresql.org, installed last cygwin) with the data dir from old server,
Hi,
Currently, the SQL statement that causes an error condition is reported
in the server log. On the other hand, the bind-parameter is not reported
as following.
FATAL: terminating connection due to administrator command
STATEMENT: UPDATE tbl SET name = $1 WHERE id = $2
LOG: shutting down
alexander lunyov wrote:
Andreas Pflug wrote:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
Maybe you should just dump schema and data separately
Tom Lane wrote:
Martin Pihlak [EMAIL PROTECTED] writes:
Changing statement result type is also currently prohibited in
StorePreparedStatement. There maybe good reasons for this,
How about the SQL spec says so?
Admittedly, it's a bit of a jump from views to prepared statements,
but the
Guillaume Smet wrote:
On Fri, Aug 15, 2008 at 11:42 AM, alexander lunyov [EMAIL PROTECTED] wrote:
i didn't find anything like postgresql.conf on old server. Right now i'm
tried to start 6.5.3 on windows (downloaded binary from ftp archive on
postgresql.org, installed last cygwin) with the data
Hi,
Peter Sampson wrote:
Hi,
I would like to use one of the XML rendering functions like
table_to_xml_and_xmlschema OR table_to_xml and render the output via
XSL, preferably in one query.
What do you think would be the benefit of doing that?
I've searched the mailing lists,site, docs and
Tino, thanks for your reply
I would like to use one of the XML rendering functions like
table_to_xml_and_xmlschema OR table_to_xml and render the output via XSL,
preferably in one query.
What do you think would be the benefit of doing that?
My main reason would be to embed all of the
Am Thursday, 14. August 2008 schrieb Pavel Stehule:
I propose enhance current syntax that allows to specify label for any
function parameter:
fcename(expr [as label], ...)
fcename(colname, ...)
I would to allow same behave of custom functions like xmlforest function:
postgres=# select
Am Friday, 15. August 2008 schrieb Peter Sampson:
I've searched the mailing lists,site, docs and Google -- to no avail. Also,
I see that xslt_process (from xml2) will be deprecated going forward. We're
building an app that will be used for a long time into the future, and I'd
like to keep it
2008/8/15 Peter Eisentraut [EMAIL PROTECTED]:
Am Thursday, 14. August 2008 schrieb Pavel Stehule:
I propose enhance current syntax that allows to specify label for any
function parameter:
fcename(expr [as label], ...)
fcename(colname, ...)
I would to allow same behave of custom functions
With this query you can view all casts involving varchar:
SELECT castsource::regtype, casttarget::regtype, castfunc::regprocedure,
castcontext FROM pg_cast WHERE 'varchar'::regtype IN (castsource, casttarget)
ORDER BY 1, 2;
Note that varchar mostly borrows the cast functions from the text
Am Friday, 15. August 2008 schrieb Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
How is this supposed to interact with argument names ?
Yeah, the real problem with this proposal is that it conscripts a syntax
that we'll probably want to use in the future for argument-name-based
An open task in replacing contrib/xml2 is the XSLT support, which the current
core implementation lacks altogether. I am known to often be in favor of a
lean core, so I have so far been hesitant to push this further, but we should
eventually come up with an implementation for the users' sake.
On Fri, Aug 15, 2008 at 04:11:11PM +0300, Peter Eisentraut wrote:
An open task in replacing contrib/xml2 is the XSLT support, which
the current core implementation lacks altogether. I am known to
often be in favor of a lean core, so I have so far been hesitant to
push this further, but we
Hello
2008/8/15 Peter Eisentraut [EMAIL PROTECTED]:
Am Friday, 15. August 2008 schrieb Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
How is this supposed to interact with argument names ?
Yeah, the real problem with this proposal is that it conscripts a syntax
that we'll probably want
Peter Eisentraut [EMAIL PROTECTED] writes:
Note that varchar mostly borrows the cast functions from the text type.
The
exception is that there is a separate set of SQL-level functions for casting
between name and varchar and vice versa. But these are actually matched to
the same C-level
Peter Eisentraut [EMAIL PROTECTED] writes:
Random googling shows me that Oracle appears to use a syntax like
name = value
This is actually a feature that I would like to see implemented soonish, so
if
anyone has input on the possible syntax consequences, please comment.
We've been over
Peter Eisentraut [EMAIL PROTECTED] writes:
An open task in replacing contrib/xml2 is the XSLT support, which the current
core implementation lacks altogether. I am known to often be in favor of a
lean core, so I have so far been hesitant to push this further, but we should
eventually come
alexander lunyov [EMAIL PROTECTED] writes:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket.
It won't work anyway: modern versions of pg_dump are only designed to
work with servers back to 7.0. I see from the rest of the thread
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
An open task in replacing contrib/xml2 is the XSLT support, which the current
core implementation lacks altogether. I am known to often be in favor of a
lean core, so I have so far been hesitant to push this further, but we
Fujii Masao [EMAIL PROTECTED] writes:
The bind-parameter is useful information for debugging. So, I made
the small patch which reports the bind-parameter together with
the SQL statement on an error.
You can't invoke user-defined I/O functions in an already-failed
transaction. For that matter,
Andreas Pflug [EMAIL PROTECTED] writes:
I wonder if you need these self defined aggregates at all, most or all
of them are in 8.3 already.
They aren't self defined in 6.5 either. I think what is happening
is that he's trying to force a 7.x pg_dump to dump from the 6.5 server
(with -i no
Magnus Hagander wrote:
Magnus Hagander wrote:
[about the ability to use different maps for ident auth, gss and krb
auth for example]
It wouldn't be very easy/clean to do that w/o breaking the existing
structure of pg_ident though, which makes me feel like using seperate
files is
Andrew Dunstan [EMAIL PROTECTED] writes:
Peter Eisentraut [EMAIL PROTECTED] writes:
An open task in replacing contrib/xml2 is the XSLT support, which the
current
core implementation lacks altogether.
well, contrib/xml2/xslt_proc.c has 172 lines. So I suggest we just
import that to core
Josh Berkus wrote:
Greg,
Well that's going to depend on the application But I suppose there's
nothing wrong with having options which aren't always a good idea to use.
The
real question I guess is whether there's ever a situation where it would be
a
good idea to use this. I'm
Bruce Momjian wrote:
Josh Berkus wrote:
...simple web applications, where
queries are never supposed to take more than 50ms. If a query turns up
with an estimated cost of 100, then you know something's wrong;
...
How about a simpler approach that throws an error or warning for
Ron Mayer wrote:
Bruce Momjian wrote:
Josh Berkus wrote:
...simple web applications, where
queries are never supposed to take more than 50ms. If a query turns up
with an estimated cost of 100, then you know something's wrong;
...
How about a simpler approach that throws
On Thu, Aug 14, 2008 at 05:57:26PM -0500, Decibel! wrote:
FWIW, there is desire to be able to re-order columns within real
tables, too. But before that can happen we need to divorce
presentation order from on-page order (which is actually desirable
for other reasons), but that's an
Simon Riggs wrote:
When primary server fails, it would be good if the clients connected to
the primary knew to reconnect to the standby servers automatically.
We might want to specify that centrally and then send the redirection
address to the client when it connects. Sounds like lots of
Martijn van Oosterhout wrote:
On Thu, Aug 14, 2008 at 05:57:26PM -0500, Decibel! wrote:
FWIW, there is desire to be able to re-order columns within real
tables, too. But before that can happen we need to divorce
presentation order from on-page order (which is actually desirable
for
Bruce Momjian wrote:
Magnus Hagander wrote:
Magnus Hagander wrote:
[about the ability to use different maps for ident auth, gss and krb
auth for example]
It wouldn't be very easy/clean to do that w/o breaking the existing
structure of pg_ident though, which makes me feel like using
On Fri, 2008-08-15 at 12:24 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
When primary server fails, it would be good if the clients connected to
the primary knew to reconnect to the standby servers automatically.
We might want to specify that centrally and then send the redirection
Magnus Hagander wrote:
To address Magnus' specific question, right now we store the pg_hba.conf
tokens as strings in the postmaster. I am fine with storing them in a
more native format and throwing errors for values that don't convert.
What would concern me is calling lots of 3rd party
On Fri, 2008-08-15 at 10:01 -0400, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Random googling shows me that Oracle appears to use a syntax like
name = value
This is actually a feature that I would like to see implemented soonish, so
if
anyone has input on the
Simon Riggs wrote:
Implementation would be to make PQreset() try secondary connection if
the primary one fails to reset. Of course you can program this manually,
but the feature is that you wouldn't need to, nor would you need to
request changes to 27 different interfaces either.
On Fri, 2008-08-15 at 14:54 +0200, Pavel Stehule wrote:
2008/8/15 Peter Eisentraut [EMAIL PROTECTED]:
Am Thursday, 14. August 2008 schrieb Pavel Stehule:
I propose enhance current syntax that allows to specify label for any
function parameter:
fcename(expr [as label], ...)
Bruce Momjian [EMAIL PROTECTED] writes:
Ron Mayer wrote:
Seems less fool-proof to me.
My point is that people should _know_ they are using a cartesian
product, and a warning would do that for users who have no need for a
cartesian product and want to be warned about a possible error.
There
My point is that people should _know_ they are using a cartesian
product, and a warning would do that for users who have no need for a
cartesian product and want to be warned about a possible error.
I think Cartesian products are a red herring. Cartesian products are
primarily bad if they
We have got a whole bunch of functions in the system that accept
arguments of type internal, where the actual meaning of internal
varies wildly (it's generally some non-SQL-visible data structure).
While (I believe that) SQL users cannot call any such functions
directly, they could still cause all
On Aug 15, 2008, at 15:12, Tom Lane wrote:
The cleanest solution I can think of is to invent some more
pseudotypes
that act just like INTERNAL, and then to require non-privileged CREATE
commands to reference functions that take one of these types instead
of bare INTERNAL. There is a
Bruce,
How about a simpler approach that throws an error or warning for
cartesian products? That seems fool-proof.
Well, throwing a warning is pretty useless for an unattended application.
Also, it's perfectly possible to write queries which will never complete
without a cartesian join.
Thanks, applied.
---
Gregory Stark wrote:
We're currently printing the warning about connecting to the wrong version of
the server *before* syncing variables. On reconnecting this results in using
the *old* server
Simon Riggs wrote:
On Thu, 2008-06-26 at 13:42 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
We can check for removal of a rel by...
OT comment: I just found a blog about Oracle's optimizermagic, which is
quite interesting. I notice there is a blog there about join
Merlin Moncure wrote:
On Thu, Jul 31, 2008 at 1:52 PM, claudio lezcano [EMAIL PROTECTED] wrote:
Hi everybody
Iam traying to build libpq.lib and libpq.dll library using Borland c++ 5.5
and i got these error:
Error libpq.rc 1 11: Cannot open file: winver.h
I opened the libpq.rc file
Added to TODO:
* Prevent query cancel packets from being replayed by an attacker,
especially when using SSL
http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php
---
Heikki Linnakangas wrote:
It
Bruce Momjian wrote:
Where are we on this patch?
I think I submitted the patch before its time. The project opened a big
can of worms with the XML output. I'd like to rework it with some of
the comments I received.
The work there was some prep-work for the planner visualizer I've been
Where are we on this patch?
---
[EMAIL PROTECTED] wrote:
I just posted a patch addressing the TODO item:
Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
This is a modified patch originally
Where are we on this patch?
---
Reini Urban wrote:
Dave Page schrieb:
On Tue, Jun 24, 2008 at 9:32 AM, Magnus Hagander [EMAIL PROTECTED] wrote:
Yes.
As in the cygwin build does build. Nobody really has verified if
58 matches
Mail list logo
