is
that it's pre-installed on more OSes than Python is.
I think most (if not all) modern OS's standard setup includes both perl
and python. Except of course windows which probably includes neither.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL
- an agent running on the server, started
over ssh and GUI interface running on users workstation which talk to
said agent.
And I'd suggest you use wxPython for GUI part if you want a relatively
modern look.
--
Hannu Krosing http://www.2ndQuadrant.com
On Mon, 2008-11-03 at 12:42 -0500, Greg Smith wrote:
On Mon, 3 Nov 2008, Hannu Krosing wrote:
And I'd suggest you use wxPython for GUI part if you want a relatively
modern look.
wxPython is GPL licensed and not popular enough to be available on a lot
of systems already.
Wikipedia says
On Mon, 2008-11-03 at 19:07 -0500, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
On Sat, 2008-11-01 at 06:13 +0200, Hannu Krosing wrote:
This version is quite rough, though passes tests here.
I will clean it up more during commitfest.
probably still more things to do
On Sat, 2008-11-01 at 06:13 +0200, Hannu Krosing wrote:
attached is a patch which enables plpython to recognize function with
multiple OUT params as returning a record
Overrides previous patch.
Fixed some bugs, added regression tests.
This version is quite rough, though passes tests here
.
Any hope of getting pl/proxy using this submitted for 8.4 ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
=#
py=# select * from addsub(1,2);
o1 | o2
+
3 | -1
(1 row)
This version is quite rough, though passes tests here.
I will clean it up more during commitfest.
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
On Tue, 2008-10-28 at 22:37 -0300, Alvaro Herrera wrote:
Hannu Krosing wrote:
On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote:
The two obvious problems with the existing MCP architecture is:
1. Single point of failure
For async replication there is always SPoF, at least
On Tue, 2008-10-28 at 22:16 -0700, Joshua D. Drake wrote:
Alvaro Herrera wrote:
Hannu Krosing wrote:
On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote:
Will there be an helper application for setting up and configuring
changes in replication. or will it all be done using added SQL
On Wed, 2008-10-29 at 09:01 -0700, Joshua D. Drake wrote:
On Wed, 2008-10-29 at 12:02 +0200, Hannu Krosing wrote:
On Tue, 2008-10-28 at 22:16 -0700, Joshua D. Drake wrote:
Alvaro Herrera wrote:
Case in point. To replicate a table currently you do this:
ALTER TABLE foo ENABLE
On Wed, 2008-10-29 at 09:40 -0700, David Fetter wrote:
Folks,
Please find enclosed a WIP patch to add the ability for functions to
see the qualifiers of the query in which they're called. It's not
working just yet, and I'm not sure how best to get it working, but I'd
like to see this as
for theses args during planning and also
can advise function about strategies once the plan is chosen.
That would be something which could be very useful for SQL/MED
implementation as well.
-
Hannu
--
--
Hannu Krosing http://www
On Wed, 2008-10-29 at 10:33 -0700, Joshua D. Drake wrote:
On Wed, 2008-10-29 at 19:17 +0200, Hannu Krosing wrote:
On Wed, 2008-10-29 at 09:40 -0700, David Fetter wrote:
Folks,
Please find enclosed a WIP patch to add the ability for functions to
see the qualifiers of the query
that that for
vacuum.
Seems like we could write approximately half the amount
of data that we do.
Surely we can come up with a better plan than that one?
---
Hannu Krosing
http://www.2ndQuadrant.com
PostgreSQL Scalability Training, Services and Support
--
Sent via pgsql-hackers mailing
On Tue, 2008-10-28 at 10:10 +, Simon Riggs wrote:
On Tue, 2008-10-28 at 11:45 +0200, Hannu Krosing wrote:
On Tue, 2008-10-28 at 08:49 +, Simon Riggs wrote:
Looking at a VACUUM's WAL records makes me think twice about the way we
issue a VACUUM.
1. First we scan the heap
On Tue, 2008-10-28 at 14:28 +0200, Heikki Linnakangas wrote:
Hannu Krosing wrote:
On Tue, 2008-10-28 at 10:10 +, Simon Riggs wrote:
On Tue, 2008-10-28 at 11:45 +0200, Hannu Krosing wrote:
On Tue, 2008-10-28 at 08:49 +, Simon Riggs wrote:
Looking at a VACUUM's WAL records makes me
On Mon, 2008-10-27 at 13:42 -0700, Joshua Drake wrote:
With the recent open sourcing of Replicator, the team has been trying
to come up with ways to ensure an open development process. In that
light we have decided to have our first release 1.9 meeting on
Freenode. All people interested in
On Tue, 2008-10-28 at 11:01 -0700, Joshua Drake wrote:
On Tue, 28 Oct 2008 19:46:42 +0200
Hannu Krosing [EMAIL PROTECTED] wrote:
On Mon, 2008-10-27 at 13:42 -0700, Joshua Drake wrote:
With the recent open sourcing of Replicator, the team has been
trying to come up with ways to ensure
On Tue, 2008-10-28 at 15:18 -0700, Joshua Drake wrote:
On Tue, 28 Oct 2008 19:46:42 +0200
Hannu Krosing [EMAIL PROTECTED] wrote:
The current topics are:
* New MCP architecture
What's new ?
I have some doubts about the current architecture based on my reading
on functionality and get the few
system (?) tables and functions done, and worry about parser changes
once the actual functionality is field tested.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting
On Mon, 2008-10-27 at 17:00 +0900, ITAGAKI Takahiro wrote:
Martin Pihlak [EMAIL PROTECTED] wrote:
ITAGAKI Takahiro wrote:
I'd like to submit pg_stat_statements contrib module
Nice work! There is one feature I'd like to request -- we need to be able
to also track nested statements.
On Fri, 2008-10-24 at 00:52 -0400, Jonah H. Harris wrote:
While we could build an
abstract prefetch interface and simply use fadvise for it now (rather
than OS-specific code), I don't see an easy win in any case.
When building an abstract interface, always use at least two
implementations (I
On Thu, 2008-10-16 at 18:52 +0300, Heikki Linnakangas wrote:
Also, I can't help thinking that this would be a lot simpler if we just
treated all subtransactions the same as top-level transactions. The only
problem with that is that there can be a lot of subtransactions, which
means that
On Fri, 2008-09-05 at 15:39 +0300, Marko Kreen wrote:
In the previous discussion there was mentioned that Postgres should
move to the SQL-MED direction in remote connection handling.
SQL-MED specifies that connections should have names and referenced
everywhere using names.
Where did you
On Tue, 2008-10-21 at 21:05 +0300, Martin Pihlak wrote:
Hannu Krosing wrote:
In my brief reading of SQL-MED spec I could only find info on defining
FOREIGN SERVER and FOREIGN-DATA WRAPPER and nowhere in these could one
define connection parameters like username and password
6 | Aachen| 98569
7 | Aachen's | 98569
8 | Aaliyah | 98569
9 | Aaliyah's | 98569
10 | Aaron | 98569
(10 rows)
-
Hannu Krosing
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Sun, 2008-10-12 at 14:39 -0700, David E. Wheeler wrote:
On Oct 12, 2008, at 14:11, Tom Lane wrote:
You'd have to parse the result of version().
As I figured. This is what I'm trying:
if performance is not critical, then you could use this:
hannu=# create or replace function
On Tue, 2008-10-14 at 19:04 +0200, Andreas Joseph Krogh wrote:
On Tuesday 14 October 2008 18:19:07 Hannu Krosing wrote:
On Tue, 2008-10-14 at 11:05 +0200, Andreas Joseph Krogh wrote:
Hi all.
This is not very hackers-related, but related to the topic of
window-funcitons, which seems
On Tue, 2008-10-14 at 08:33 -0700, David E. Wheeler wrote:
Well, the C version I borrowed from dumpitils seems to work great. Any
reason I shouldn't stay with that?
SQL is the only PL available by default, no need to compile or install
anything.
It can be written more effectively in almost
On Tue, 2008-10-14 at 09:53 -0700, David E. Wheeler wrote:
On Oct 14, 2008, at 08:33, David E. Wheeler wrote:
Well, the C version I borrowed from dumpitils seems to work great.
Any reason I shouldn't stay with that?
Also, here's a simpler SQL version, for those following along at home:
On Wed, 2008-10-08 at 20:56 +0200, A. Kretschmer wrote:
am Wed, dem 08.10.2008, um 14:29:23 -0400 mailte Alvaro Herrera folgendes:
Hi,
Trigger functions are supposed to be able to be called only as triggers,
but apparently the check is not working in CVS HEAD:
alvherre=# create or
On Thu, 2008-10-02 at 09:35 +0300, Heikki Linnakangas wrote:
Jonah H. Harris wrote:
Rather than potentially letting this slide past 8.4, I threw together
an extremely quick-hack patch at the smgr-layer for block-level
checksums.
One hard problem is how to deal with torn pages with
On Tue, 2008-09-30 at 17:13 -0400, [EMAIL PROTECTED] wrote:
I believe the idea was to make this as non-invasive as possible. And
it would be really nice if this could be enabled without a dump/
reload (maybe the upgrade stuff would make this possible?)
--
It's all about the
On Sun, 2008-09-28 at 04:03 +0300, Greg Stark wrote:
Iirc the reason for this fuzziness came from the SQL spec definition
of IS NULL for rows. As long as you maintain that level of spec-
compliance I don't think there are any other important constraints on
pg behaviour.
What does SQL
On Sat, 2008-09-27 at 14:56 -0400, Tom Lane wrote:
I looked a bit at the bug report here:
http://archives.postgresql.org/pgsql-bugs/2008-09/msg00164.php
ISTM that the fundamental problem is that plpgsql doesn't distinguish
properly between a null row value (eg, null::somerowtype) and a
row
On Mon, 2008-09-22 at 07:53 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I think the issue is identifying the problem. Reading the title of the
post, I think Tom says no to *deleting* the toast table. He also says
no to cleaning the table as part of DROP COLUMN. That still
On Sun, 2008-09-21 at 12:05 -0400, Tom Lane wrote:
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
we came across a database where a table had a toasted table,
keeping huge amounts of disk space allocated. However,
the table's current definition didn't explain why there was
a toasted table.
everything
to Intercal.
We should rewrite it to something that has no visual noise, so
attracting new developers would be easier.
My choice would be whitespace , see
http://en.wikipedia.org/wiki/Whitespace_(programming_language)
-
Hannu Krosing
--
Sent via pgsql-hackers mailing
On Sat, 2008-09-20 at 09:06 -0400, D'Arcy J.M. Cain wrote:
On Sat, 20 Sep 2008 13:47:10 +0300
Hannu Krosing [EMAIL PROTECTED] wrote:
On Fri, 2008-09-19 at 16:37 -0400, D'Arcy J.M. Cain wrote:
I don't think that we should rush into any one language without
checking the alternatives
On Fri, 2008-09-12 at 09:45 +0100, Simon Riggs wrote:
On Thu, 2008-09-11 at 15:42 +0300, Heikki Linnakangas wrote:
Gregory Stark wrote:
b) vacuum on the server which cleans up a tuple the slave has in scope
has to
block WAL reply on the slave (which I suppose defeats the purpose of
On Fri, 2008-09-12 at 11:21 +0200, Csaba Nagy wrote:
On Fri, 2008-09-12 at 09:38 +0100, Simon Riggs wrote:
If you request a block, we check to see whether there is a lookaside
copy of it prior to the tuple removals. We then redirect the block
request to a viewpoint relation's block. Each
On Fri, 2008-09-12 at 11:19 +0100, Simon Riggs wrote:
On Thu, 2008-09-11 at 01:07 +0100, Simon Riggs wrote:
Transaction snapshots is probably the most difficult problem for Hot
Standby to resolve.
In summary of thread so far:
When queries on standby run for significantly longer than
On Fri, 2008-09-12 at 13:53 +0300, Hannu Krosing wrote:
4. Slave keeps copies of removed pages or rows when WAL apply removes
old versions .
Possible ways to do this
* inside Slave - have some backup store tied to OldestXmin intervals
* variant 1 - have one global store, accessed
On Fri, 2008-09-12 at 12:31 +0300, Hannu Krosing wrote:
On Fri, 2008-09-12 at 09:45 +0100, Simon Riggs wrote:
On Thu, 2008-09-11 at 15:42 +0300, Heikki Linnakangas wrote:
Gregory Stark wrote:
b) vacuum on the server which cleans up a tuple the slave has in scope
has to
block
On Fri, 2008-09-12 at 13:54 +0200, Csaba Nagy wrote:
I think that enabling long-running queries this way is both
low-hanging
fruit (or at least medium-height-hanging ;) ) and also consistent to
PostgreSQL philosophy of not replication effort. As an example we trust
OS's file system cache
On Fri, 2008-09-12 at 17:08 +0300, Heikki Linnakangas wrote:
Simon Riggs wrote:
It should be clear that to make this work you must run with a base
backup that was derived correctly on the current master. You can do that
by re-copying everything, or you can do that by just shipping changed
On Fri, 2008-09-12 at 17:45 +0100, Simon Riggs wrote:
On Fri, 2008-09-12 at 17:11 +0200, Csaba Nagy wrote:
Why not have a design where the slave is in control for it's own data ?
I mean the slave...
The slave only exists because it is a copy of the master. If you try to
startup a slave
On Thu, 2008-09-11 at 09:24 +0300, Heikki Linnakangas wrote:
I like the idea of acquiring snapshots locally in the slave much more.
As you mentioned, the options there are to defer applying WAL, or cancel
queries.
More exotic ways to defer applying WAL include using some smart
filesystems
On Wed, 2008-09-10 at 15:15 +0900, Fujii Masao wrote:
On Wed, Sep 10, 2008 at 12:26 AM, Heikki Linnakangas
[EMAIL PROTECTED] wrote:
If a slave falls behind, how does it catch up? I guess you're saying that it
can't fall behind, because the master will block before that happens. Also
in
On Wed, 2008-09-10 at 09:27 +0300, Volkan YAZICI wrote:
On Tue, 9 Sep 2008, David Fetter [EMAIL PROTECTED] writes:
AFAICS, PostgreSQL is not keeping info about when a table, database,
sequence, etc was created. We cannot get that info even from OS,
since CLUSTER or VACUUM FULL may change
On Wed, 2008-09-10 at 10:06 +0200, Markus Wanner wrote:
Hi,
Simon Riggs wrote:
1. Standby contacts primary and says it would like to catch up, but is
currently at point X (which is a point at, or after the first consistent
stopping point in WAL after standby has performed its own crash
On Wed, 2008-09-10 at 08:15 +0100, Simon Riggs wrote:
Any working solution needs to work for all required phases. If you did
it this way, you'd never catch up at all.
When you first make the copy, it will be made at time X. The point of
consistency will be sometime later and requires WAL
On Wed, 2008-09-10 at 07:13 -0400, Robert Haas wrote:
I'm not planner guru but it seems to me that BETWEEN clause could be
rewritten as a IN clause for integer data types and small interval.
Where should the line be drawn.
Define small :)
When the estimated cost is lower?
You still
On Tue, 2008-09-09 at 12:40 -0700, daveg wrote:
I'd be very interested in seeing a last schema modification time for pg_class
objects. I don't care about it being preserved over dump and restore as my
use case is more to find out when a table was created with a view to finding
out if it is
On Thu, 2008-09-04 at 11:51 -0400, Andrew Sullivan wrote:
On Thu, Sep 04, 2008 at 07:01:18AM -0700, Steve Atkins wrote:
Settings in postgresql.conf are currently case-insensitive. Except
for the units.
And, of course, filenames when you are using a case-sensitive
filesystem. Because
On Thu, 2008-09-04 at 09:29 -0400, Andrew Sullivan wrote:
On Thu, Sep 04, 2008 at 01:26:44AM +0300, Hannu Krosing wrote:
So Andrews opinion was that Mb (meaning Mbit) is different from MB (for
megabyte) and that if someone thinks that we define shared buffers in
megabits can get confused
On Tue, 2008-09-02 at 16:50 +0300, Peter Eisentraut wrote:
Gregory Stark wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Marko Kreen wrote:
In the meantime, here is simple patch for case-insensivity.
You might be able to talk me into accepting various unambiguous, common
On Wed, 2008-09-03 at 07:52 -0700, Joshua D. Drake wrote:
Hannu Krosing wrote:
On Tue, 2008-09-02 at 16:50 +0300, Peter Eisentraut wrote:
Gregory Stark wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Are you really afraid that someone would want to use mb to mean
millibits
On Wed, 2008-09-03 at 08:20 -0700, Joshua D. Drake wrote:
Greg Stark wrote:
I don't think worrying about the message we send to users is reasonable.
We can take responsibilty for the messages we output but punishing our
users to teach them a lesson is being actively user-hostile
There
On Wed, 2008-09-03 at 09:10 -0700, Joshua Drake wrote:
If someone doesn't know the difference between Mb and MB on a
production system, I would not want them anywhere near any instance of
a production system.
I for one can make the difference, once I can zen that we are in a
domain, where
On Wed, 2008-09-03 at 13:48 -0400, Alvaro Herrera wrote:
Hannu Krosing escribió:
On Wed, 2008-09-03 at 09:10 -0700, Joshua Drake wrote:
If we are going to make sweeping statements (anyone on this thread)
about user-hostile and most people, then we better define what those
mean
On Wed, 2008-09-03 at 11:45 -0700, Joshua Drake wrote:
On Wed, 3 Sep 2008 19:36:19 +0100
Greg Stark [EMAIL PROTECTED] wrote:
Sure if people want to do it the right way more power to them. What
you're talking about is punishing people when they don't live up to
your standards.
I
On Wed, 2008-09-03 at 20:01 -0400, Alvaro Herrera wrote:
Hannu Krosing escribió:
I mean, there is no known written standard, which says that Mb is
megabit, not megabyte or that you can (or can't) write kilo as K, but
some people just believe that kB is the Way and allowing people
On Mon, 2008-09-01 at 11:15 +0200, Pavel Stehule wrote:
2008/9/1 Magnus Hagander [EMAIL PROTECTED]:
Pavel Stehule wrote:
Hello
2008/8/31 Hannu Krosing [EMAIL PROTECTED]:
hannu=# create or replace function ffa(a int, a int) returns int
language plpgsql as $$begin return a + a; end
On Sun, 2008-08-31 at 13:17 -0400, Tom Lane wrote:
The current result from buildfarm member pigeon
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=pigeondt=2008-08-31%2008:04:54
shows a symptom I've noticed a few times before: everything is fine
except that one select * from sequence shows
It seems that we allow several function arguments to have same
name (or is it label :)
hannu=# create or replace function ff(a int, a int) returns int language
plpgsql as $$begin return $1+$2; end;$$;
CREATE FUNCTION
hannu=# select ff(1,1);
ff
2
(1 row)
hannu=# select ff(1,2);
ff
On Fri, 2008-08-29 at 01:29 -0400, Tom Lane wrote:
Greg Smith [EMAIL PROTECTED] writes:
On Fri, 29 Aug 2008, Tom Lane wrote:
You're ignoring the fact that D'Arcy's patch doesn't output valid ReST.
It outputs something that might pass for ReST, but only so long as there
are no special
On Sun, 2008-08-24 at 08:05 +0200, Pavel Stehule wrote:
2008/8/23 Tom Lane [EMAIL PROTECTED]:
Hannu Krosing [EMAIL PROTECTED] writes:
On Sat, 2008-08-23 at 08:21 +0200, Pavel Stehule wrote:
record or hash table - it's implementation - second step. We have to
find syntax and semantic now
On Sat, 2008-08-23 at 14:42 -0400, Andrew Dunstan wrote:
D'Arcy J.M. Cain wrote:
On Thu, 21 Aug 2008 21:04:07 -0400
D'Arcy J.M. Cain [EMAIL PROTECTED] wrote:
There's still the question of whether this covers any needs that aren't
met just as well by XML or CSV output formats.
On Sat, 2008-08-23 at 08:21 +0200, Pavel Stehule wrote:
Hello
2008/8/22 Hannu Krosing [EMAIL PROTECTED]:
On Thu, 2008-08-21 at 23:41 -0500, Decibel! wrote:
On Aug 20, 2008, at 8:26 AM, Pavel Stehule wrote:
How about we poll -general and see what people say? I'll bet Tom a
beer
On Fri, 2008-08-22 at 12:42 -0400, Andrew Dunstan wrote:
depends if you think hacking the bison grammar is a beginner task.
It may be anything from beginners task to quite complex . Some things
are just copypaste.
-
Hannu
--
Sent via pgsql-hackers mailing list
On Thu, 2008-08-21 at 23:41 -0500, Decibel! wrote:
On Aug 20, 2008, at 8:26 AM, Pavel Stehule wrote:
How about we poll -general and see what people say? I'll bet Tom a
beer that no one replies saying they've created a = operator (unless
maybe PostGIS uses it).
Does Oracle use = for
On Tue, 2008-08-19 at 19:45 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
If there is plan invalidation then you just change called1() to return
one more field and that's it - no juggling with C) and D) and generally
less things that can go wrong.
That is a pure flight
On Wed, 2008-08-20 at 08:50 -0400, Andrew Dunstan wrote:
Asko Oja wrote:
I do get the impression that Tom who would prefer to get all the pl's
out of PostgreSQL and live happily ever after with pure SQL standard.
I have not seen the slightest evidence of this, and don't believe it
On Mon, 2008-08-18 at 22:41 +0200, Pavel Stehule wrote:
2008/8/18 Hannu Krosing [EMAIL PROTECTED]:
On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
2008/8/18 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
Le lundi 18 août 2008, Andrew Dunstan a écrit :
On Sat, Aug 16, 2008 at 09
On Mon, 2008-08-18 at 20:29 -0400, Tom Lane wrote:
Asko Oja [EMAIL PROTECTED] writes:
For users of stored procedures it is protection from downtime. For Skype it
has been around 20% of databse related downtime this year.
Perhaps Skype needs to rethink how they are modifying functions.
Why
On Tue, 2008-08-19 at 12:42 +0200, Pavel Stehule wrote:
2008/8/19 Hannu Krosing [EMAIL PROTECTED]:
On Mon, 2008-08-18 at 22:41 +0200, Pavel Stehule wrote:
2008/8/18 Hannu Krosing [EMAIL PROTECTED]:
On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
2008/8/18 Dimitri Fontaine [EMAIL
On Tue, 2008-08-19 at 12:40 -0400, Tom Lane wrote:
Back in April we changed EXPLAIN VERBOSE to not dump the internal plan
tree anymore, on the grounds that non-hackers didn't want that info and
hackers could get it with debug_print_plan and related variables.
Well, now that I've tried to do
On Tue, 2008-08-19 at 21:26 +0200, Dimitri Fontaine wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 19 août 08 à 19:06, Tom Lane a écrit :
Dimitri Fontaine [EMAIL PROTECTED] writes:
Another thing I do not understand well is how people are expected
to work in
8.3 with
On Tue, 2008-08-19 at 16:03 -0400, Robert Haas wrote:
Another thing I do not understand well is how people are expected to work in
8.3 with a function based API, without hitting Skype problems. I'm having a
All database-driven applications have this problem. Any time you have
a database
On Tue, 2008-08-19 at 16:56 -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
The actual criterion is not really new user-visible feature versus
bug fix. It's more an attempt at measuring how large a potential
impact the change has. The patch I saw was introducing a whole
On Tue, 2008-08-19 at 16:56 -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
The actual criterion is not really new user-visible feature versus
bug fix. It's more an attempt at measuring how large a potential
impact the change has. The patch I saw was introducing a whole
On Mon, 2008-08-18 at 08:53 +0200, Pavel Stehule wrote:
2008/8/17 Hannu Krosing [EMAIL PROTECTED]:
On Sun, 2008-08-17 at 17:59 +0200, Pavel Stehule wrote:
Hannu
it's not possible in plpgsql, because we are not able iterate via record.
just add function for iterating over record
On Mon, 2008-08-18 at 10:51 +0300, Peter Eisentraut wrote:
Am Saturday, 16. August 2008 schrieb Hannu Krosing:
A label is the same thing as variable/attribute/argument name in
all programming languages I can think of. Why do you need two kinds of
argument names in postgreSQL ?
maybe
On Mon, 2008-08-18 at 11:19 -0400, Bruce Momjian wrote:
Is this a TODO?
I don't think we have a TODO yet.
Maybe a TBD :)
---
Hannu Krosing wrote:
On Mon, 2008-08-18 at 08:53 +0200, Pavel Stehule wrote:
2008/8/17
On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
2008/8/18 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
Le lundi 18 août 2008, Andrew Dunstan a écrit :
On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
This is not the kind of patch we put into stable branches.
So what?
On Sun, 2008-08-17 at 08:06 +0200, Pavel Stehule wrote:
2008/8/16 Decibel! [EMAIL PROTECTED]:
On Aug 15, 2008, at 1:20 PM, Hannu Krosing wrote:
value AS name, on the other hand, accomplishes the same in a more
SQL-looking fashion with no new reserved word (since AS is already
fully
On Sun, 2008-08-17 at 11:08 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Actually the most natural syntax to me is just f(name=value) similar
to how UPDATE does it. It has the added benefit of _not_ forcing us to
make a operator reserved (AFAIK = can't be used to define
should
be
[name:Zdenek,age:30]
2008/8/17 Hannu Krosing [EMAIL PROTECTED]:
On Sun, 2008-08-17 at 11:08 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Actually the most natural syntax to me is just f(name=value) similar
to how UPDATE does it. It has the added benefit
On Sun, 2008-08-17 at 18:24 -0400, Robert Haas wrote:
Actually the most natural syntax to me is just f(name=value) similar
to how UPDATE does it. It has the added benefit of _not_ forcing us to
make a operator reserved (AFAIK = can't be used to define new ops)
The problem with this is
On Sat, 2008-08-16 at 08:44 +0200, Pavel Stehule wrote:
Hello
value AS name, on the other hand, accomplishes the same in a more
SQL-looking fashion with no new reserved word (since AS is already
fully reserved).
would it be more natural / SQL-like to use value AS name or name AS
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
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], ...)
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 from another function ?
How is this supposed
On Tue, 2008-08-05 at 16:16 +0200, Pavel Stehule wrote:
2008/8/5 Martin Pihlak [EMAIL PROTECTED]:
DROP FUNCTION
create function foo() returns integer as $$ begin return 2; end; $$
language plpgsql;
CREATE FUNCTION
execute c1;
psql:test.sql:11: ERROR: cache lookup failed for function
On Tue, 2008-08-05 at 16:17 +0200, Pavel Stehule wrote:
2008/8/5 Asko Oja [EMAIL PROTECTED]:
postgres=# create or replace function pavel ( i_param text, status OUT int,
status_text OUT text ) returns record as $$ select 200::int, 'ok'::text; $$
language sql;
CREATE FUNCTION
postgres=#
On Wed, 2008-08-06 at 12:13 +0200, Pavel Stehule wrote:
2008/8/6 Hannu Krosing [EMAIL PROTECTED]:
On Tue, 2008-08-05 at 16:17 +0200, Pavel Stehule wrote:
..
you cannot change header of function. It's same as change C header of
function without complete recompilation.
SQL is not C
On Wed, 2008-08-06 at 15:41 +0200, Pavel Stehule wrote:
2008/8/6 Hannu Krosing [EMAIL PROTECTED]:
On Wed, 2008-08-06 at 12:13 +0200, Pavel Stehule wrote:
2008/8/6 Hannu Krosing [EMAIL PROTECTED]:
On Tue, 2008-08-05 at 16:17 +0200, Pavel Stehule wrote:
..
you cannot change header
On Tue, 2008-08-05 at 07:52 +0100, Simon Riggs wrote:
On Mon, 2008-08-04 at 22:56 -0400, Tom Lane wrote:
Josh Berkus [EMAIL PROTECTED] writes:
I think the proposal was for an extremely simple works 75% of the time
failover solution. While I can see the attraction of that, the
On Mon, 2008-08-04 at 13:08 -0400, David Blewett wrote:
Hi All:
This is an off-shoot of the Do we really want to migrate plproxy and
citext into PG core distribution? thread.
On the way home from PyOhio, I had a conversation with a few people
that use Zope a lot. I happened to mention
501 - 600 of 1744 matches
Mail list logo
