On Sun, 4 Feb 2007, David Fetter wrote:
On Fri, Feb 02, 2007 at 07:01:33PM -0800, Jeremy Drake wrote:
Let me know if you see any bugs or issues with this code, and I am
open to suggestions for further regression tests ;)
I have not heard anything, so I guess at this point I should figure
Hello,
Currently PostgreSQL support set returning functions.
ANSI SQL 2003 goes with new type of functions - table functions. With
this
syntax
CREATE FUNCTION foo() RETURNS TABLE (c1 t1, ... )
PostgreSQL equal statements are:
CREATE TYPE tmptype AS (c1 t1, ...)
CREATE FUNCTION
Hi Tom,
On Tue, 6 Feb 2007, Tom Lane wrote:
Date: Tue, 06 Feb 2007 11:50:56 -0500
From: Tom Lane [EMAIL PROTECTED]
To: ohp@pyrenet.fr
Cc: pgsql-hackers list pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] misread release notes
ohp@pyrenet.fr writes:
I read the fix incorrect
On Saturday 03 February 2007, Bruce Momjian wrote:
Jan Wieck wrote:
I don't have any such paper and the proof of concept will be the
implementation of the system. I do however see enough resistance against
this proposal to withdraw the commit timestamp at this time. The new
replication
[ BCC to hackers list.]
Anyone going to the LinuxWorld Summit in New York City next week?
http://www.linuxworldsummit.com/live/14/
I am going on the 15th. PostgreSQL doesn't have a booth at the event.
--
Bruce Momjian [EMAIL PROTECTED] http://momjian.us
EnterpriseDB
If anyone is interested, let me know and I'll add this to my ToDo
list.
The Sun benchmarking team needs this. However, we need to be able to feed
the data into some kind of mass analysis ala pg_fouine so that we can do
overall performance analysis.
I've also included a PL/pgSQL
Jim Nasby wrote:
On Feb 5, 2007, at 8:19 AM, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
My suggestions would be
1. Database system has completed recovery and
2. Database system is ready to accept connections
The second was in fact the wording I had in mind, sorry for not being
What is the practical purpose of the notices emitted by DROP SOMETHING IF
EXISTS when the object in fact does not exist?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list
Bruce Momjian [EMAIL PROTECTED] writes:
[ BCC to hackers list.]
Anyone going to the LinuxWorld Summit in New York City next week?
http://www.linuxworldsummit.com/live/14/
I am going on the 15th. PostgreSQL doesn't have a booth at the event.
I'm not a hacker, just a happy user, but
Jeremy Drake [EMAIL PROTECTED] writes:
* Put together a patch to add these functions to core. I could put them
directly in regexp.c, so the support functions could stay static. My
concern here is that I don't know if there are any functions currently
in core with OUT parameters.
As of
Peter Eisentraut wrote:
What is the practical purpose of the notices emitted by DROP SOMETHING IF
EXISTS when the object in fact does not exist?
It was asked for ...
http://archives.postgresql.org/pgsql-patches/2005-11/msg00072.php
I realise that doesn't quite answer your question.
On 2/7/2007 2:37 AM, Markus Schiltknecht wrote:
Hi,
Jan Wieck wrote:
Whatever strategy one will use, in an async multimaster there are always
cases that can be resolved by rules (last update being one of them), and
some that I can't even imagine solving so far. I guess some of the cases
will
On 2/6/07, Andrew Dunstan [EMAIL PROTECTED] wrote:
If the extension installs everything in dedicated namespace(s), I think
we would want to have an option to add those namespaces easily to search
paths. Right now all we can do is to set a search path. It would be
nice, for example, to have
On 2/7/07, Nikolay Samokhvalov [EMAIL PROTECTED] wrote:
I still think that separate namespaces for extensions is a good idea
while adjusting search_path is not. I've explained my POV in details
several messages ago in this thread...
Separation of extensions with fully specified names
Nikolay Samokhvalov wrote:
I still do not understand why is it so needed.
Your argument is some apps aren't able to call functions as
schemaname.functionname(arg1, arg2, ..), right?
wrong.
I still think that separate namespaces for extensions is a good idea
while adjusting search_path is
Heap Only Tuples (HOT) is a simplification of earlier proposals for
improving the way the server handles frequent updates, based upon what's
been learned and feedback received.
Heap Only Tuples
The basic idea is that when a tuple is UPDATEd we can, in certain
circumstances,
Hi,
Jan Wieck wrote:
Are we still discussing if the Postgres backend may provide support for
a commit timestamp, that follows the rules for Lamport timestamps in a
multi-node cluster?
No. And I think you know my opinion about that by now. ;-)
It seems more like we are drifting into what
On 2/7/07, Andrew Dunstan [EMAIL PROTECTED] wrote:
Nikolay Samokhvalov wrote:
I still do not understand why is it so needed.
Your argument is some apps aren't able to call functions as
schemaname.functionname(arg1, arg2, ..), right?
wrong.
I still think that separate namespaces for
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
It'd be interesting to try to gather stats on the length of the delay
taken, but I don't see a good way to do that within the current
regression-test infrastructure.
Have it log something that will appear on the postmaster log but not
On Tue, 2007-02-06 at 23:43 +0100, Pavel Stehule wrote:
ANSI SQL 2003 goes with new type of functions - table functions. With this
syntax
...
All necessary infrastructure is done. Implementation needs propably only
small changes in parser.
...
* conformance with ansi sql 2003
Sounds good
On Wed, Feb 07, 2007 at 02:13:48PM +0100, Peter Eisentraut wrote:
What is the practical purpose of the notices emitted by DROP
SOMETHING IF EXISTS when the object in fact does not exist?
DROP ... IF EXISTS is guaranteed not to throw an error. This lets
people write idempotent scripts which run
Jan Wieck wrote:
Are we still discussing if the Postgres backend may provide support for
a commit timestamp, that follows the rules for Lamport timestamps in a
multi-node cluster?
...I thought you said in this thread that you haven't and weren't going to
work on any kind of logical proof
Nikolay Samokhvalov [EMAIL PROTECTED] writes:
We cannot use schema name as prefix for operator calling
You can, but it's kind of ugly:
regression=# SELECT 2 OPERATOR(pg_catalog.+) 2;
?column?
--
4
(1 row)
regards, tom lane
Tom Lane wrote:
We could make it cleaner by inventing a function to clear out the cached
statistics within a transaction, perhaps pg_stat_reset_snaphot() or
some such name. If anyone thinks that that would be of general
usefulness, I'll see about making it happen.
During the development of
On Wed, Feb 07, 2007 at 09:23:58AM -0500, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
* Put together a patch to add these functions to core. I could put them
directly in regexp.c, so the support functions could stay static. My
concern here is that I don't know if there are
Simon Riggs [EMAIL PROTECTED] writes:
The basic idea is that when a tuple is UPDATEd we can, in certain
circumstances, avoid inserting index tuples for a tuple. Such tuples are
marked HEAP_ONLY_TUPLE, but their storage is otherwise identical to
other tuples.
What is VACUUM FULL going to do
On Tue, 2007-02-06 at 12:33 -0600, Bruno Wolff III wrote:
Is a test going to get added to the regression tests to catch similar
regressions in the future?
While we can modify the regression tests to catch this specific problem
in the future, I wonder if there ought to be more testing of
On Wed, Feb 07, 2007 at 10:53:34 -0800,
David Fetter [EMAIL PROTECTED] wrote:
On Wed, Feb 07, 2007 at 02:13:48PM +0100, Peter Eisentraut wrote:
What is the practical purpose of the notices emitted by DROP
SOMETHING IF EXISTS when the object in fact does not exist?
DROP ... IF EXISTS is
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
We could make it cleaner by inventing a function to clear out the cached
statistics within a transaction, perhaps pg_stat_reset_snaphot() or
some such name. If anyone thinks that that would be of general
usefulness, I'll see about
Neil Conway wrote:
On Tue, 2007-02-06 at 12:33 -0600, Bruno Wolff III wrote:
Is a test going to get added to the regression tests to catch similar
regressions in the future?
While we can modify the regression tests to catch this specific problem
in the future, I wonder if there ought to
Neil Conway [EMAIL PROTECTED] writes:
While we can modify the regression tests to catch this specific problem
in the future, I wonder if there ought to be more testing of security
releases in the future. When a problem is reported, fixed, tested, and
the resulting security fix is publicly
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
We could make it cleaner by inventing a function to clear out the cached
statistics within a transaction, perhaps pg_stat_reset_snaphot() or
some such name. If anyone thinks that that would be of general
Tom Lane wrote:
None of your use-cases require tracking multiple sets of stats within a
transaction, so I don't see why bother with that when we can just add a
flush the stats call.
FWIW I'm thinking that the corresponding code for handling the backends'
stats could be simplified,
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
It'd be interesting to try to gather stats on the length of the delay
taken, but I don't see a good way to do that within the current
regression-test infrastructure.
Have it log something that will appear on the
Jim Nasby wrote:
In addition to Martijn's tsearch case, there's also PostGIS. And I
believe this is a pretty big pain for them.
Hear hear! It would be nice to dump from an old PostgreSQL/PostGIS
combination and restore to a new version combination, without taking all
the function
Alvaro Herrera [EMAIL PROTECTED] writes:
Beluga just failed:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=belugadt=2007-02-07%2019:30:01
Wow, that is a really interesting failure, because it implies that the
stats collector had seen the seqscan report but not the indexscan report:
On Wed, 7 Feb 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
* Put together a patch to add these functions to core. I could put them
directly in regexp.c, so the support functions could stay static. My
concern here is that I don't know if there are any functions
Jeremy Drake [EMAIL PROTECTED] writes:
On Wed, 7 Feb 2007, Tom Lane wrote:
As of 8.2 there are.
Could you give me the name of one in pg_proc.h so I can see how I should
go about adding one there?
select * from pg_proc where proargmodes is not null;
regards, tom lane
On Wed, 2007-02-07 at 14:17 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
The basic idea is that when a tuple is UPDATEd we can, in certain
circumstances, avoid inserting index tuples for a tuple. Such tuples are
marked HEAP_ONLY_TUPLE, but their storage is otherwise
Simon Riggs wrote:
Heap Only Tuples (HOT) is a simplification of earlier proposals for
improving the way the server handles frequent updates, based upon what's
been learned and feedback received.
Heap Only Tuples
The basic idea is that when a tuple is UPDATEd we can, in
On 2/7/07, Joshua D. Drake [EMAIL PROTECTED] wrote:
Simon Riggs wrote:
Heap Only Tuples (HOT) is a simplification of earlier proposals for
improving the way the server handles frequent updates, based upon what's
been learned and feedback received.
Uhmmm... how often is that the case? Don't
Alvaro Herrera [EMAIL PROTECTED] writes:
FWIW I'm thinking that the corresponding code for handling the backends'
stats could be simplified, removing the hack that stores it in
TopTransactionContext, and just having a call to the stats flush
function in AbortTransaction and CommitTransaction.
On 2/7/2007 12:54 PM, Markus Schiltknecht wrote:
Hi,
Jan Wieck wrote:
Are we still discussing if the Postgres backend may provide support for
a commit timestamp, that follows the rules for Lamport timestamps in a
multi-node cluster?
No. And I think you know my opinion about that by now. ;-)
Hi,
Jan Wieck wrote:
Then let me give you a little puzzle just for the fun of it.
A database containing customer contact information (among other things)
is a two node multimaster system. One is serving the customer web
portal, the other is used by the company staff including the call
If I have a multi-call SRF and a user_fctx struct allocated in the
multi_call_memory_ctx, and in the if(SRF_IS_FIRSTCALL()) block while still
in the multi_call_memory_ctx I use PG_GETARG_TEXT_P(n) to get an argument
to my function, and stash the result of this in my user_fctx struct, am I
On 2/7/2007 2:15 PM, Richard Troy wrote:
Jan Wieck wrote:
Are we still discussing if the Postgres backend may provide support for
a commit timestamp, that follows the rules for Lamport timestamps in a
multi-node cluster?
...I thought you said in this thread that you haven't and weren't
On 2/7/2007 9:27 PM, Markus Schiltknecht wrote:
Hi,
Jan Wieck wrote:
Then let me give you a little puzzle just for the fun of it.
A database containing customer contact information (among other things)
is a two node multimaster system. One is serving the customer web
portal, the other is
I find the term logical proof of it's correctness too restrictive. It
sounds like some formal academic process that really doesn't work well
for us.
What I did want to hear is a layout of how the system would work, and an
exchange of ideas until almost everyone was happy.
Also, I saw the
On 2/7/2007 10:35 PM, Bruce Momjian wrote:
I find the term logical proof of it's correctness too restrictive. It
sounds like some formal academic process that really doesn't work well
for us.
Thank you.
Also, I saw the trigger patch with no explaination of why it was
important or who would
Just thought this ought to be shared with everyone. :-)
-- Forwarded Message --
Subject: [webmaster] Its has been a great db experience with pg.
Date: Monday 01 January 2007 01:46
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Dear Sir,
We at Indian Express Newspapers (India) ,
Jan Wieck wrote:
On 2/7/2007 10:35 PM, Bruce Momjian wrote:
I find the term logical proof of it's correctness too restrictive. It
sounds like some formal academic process that really doesn't work well
for us.
Thank you.
Also, I saw the trigger patch with no explaination of why it
Patch applied. Thanks.
---
Gavin Sherry wrote:
On Tue, 5 Dec 2006, Gavin Sherry wrote:
On Thu, 30 Nov 2006, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
I wonder if we should check if the role
52 matches
Mail list logo
