Eric B. Ridge wrote:
gotcha. Stated differently, it's not volatile because, by design, it
doesn't always produce the same output for the same input.
Right. But further, it doesn't even produce the same result within a
single scan. Here's from pg_proc.h:
/*
* Symbolic values for provolatile col
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Hoo, I'm surprised no one noticed this during 7.4
> development/testing.
> The problem applies for any datatype that requires
> double alignment,
> which includes int8, float8, and timestamp as well
> as most of the
> geometric types. pg_statistic is decl
On Feb 25, 2004, at 9:07 PM, Joe Conway wrote:
Eric B.Ridge wrote:
I suppose this is obvious, but it's volatile because *other* backends
can change it while the current transaction is still in progress?
No. Other backends don't affect currval, but your own might on a
row-by-row basis. Consider:
Eric B.Ridge wrote:
I suppose this is obvious, but it's volatile because *other* backends
can change it while the current transaction is still in progress?
No. Other backends don't affect currval, but your own might on a
row-by-row basis. Consider:
regression=# create sequence seq;
CREATE SEQUEN
Many thanks to all who pointed out the usefulness of the 'ANALYZE' command
in my last question. I assumed the db admin was doing 'VACUUM ANALYZE'
after each days insert but he wasn't.
Is there a shorthand notation when performing a multi-table join and one
column is to be equaled in all tables? i
On Feb 25, 2004, at 8:02 PM, Tom Lane wrote:
Brandon Craig Rhodes <[EMAIL PROTECTED]> writes:
But this same table suddenly becomes unwilling to use an index scan if
the target value is the result of the currval() function:
currval() is considered a volatile function, therefore it is unsafe to
use
Shridhar Daithankar
<[EMAIL PROTECTED]> 25/02/2004 10:31:16
On Wednesday 25 February 2004 15:38, Paul Simpson
wrote:>> Thank you for the advice, unfortunately, that isn't an
option, you see I>> didn't write the application and so cannot control
the calls it makes. What>> I need is
Thank you for the advice, unfortunately, that isn't an option, you see I
didn't write the application and so cannot control the calls it makes. What I
need is for PG to do as it's told!
I can only think of three solutions which I'd appreciate comments / advice
on
1) Hack PG Source and
Sorry i forgot to mention:
-that you need pg 7.3 for the set-returning function feature.
-how to select from the function:
select * from _YOUR_FUNCTION(PARAMETER);
and NOT:
select _YOUR_FUNCTION(PARAMETER);
>-Ursprüngliche Nachricht-
>Von: [EMAIL PROTECTED] [mailto:pgsql-general-
>[E
Hi sylvain,
i think what you need is a so-called "set-returning-function":
if you just need sql (example with a table called user_data):
create or replace function user_info(integer)
returns setof user_data as '
select * from user_data where user_id = $1;
' language 'sql';
if you need plpgs
Dear Shelby Cain ,
Is this expected behavior or perhaps a bug?
For a novice like me can anyone please tell me
1. Will this effect my application developed on PostgreSQL
2. Will my Application break at some point I heavly use the type of
queries defined in the post.
Would be greatfull for
On Tuesday 24 February 2004 22:10, Paul Simpson wrote:
> Create Table TTATTASSOC (AssocId varchar(10), SetId varchar(10), SlotId
> int4)
> I have, therefore, come to the conclusion that the app requires table names
> in Upper case. How can I force this to work?
I believe postgresql is noisy about
On Wednesday 25 February 2004 02:36, Jeff Holle wrote:
> Will somebody on this list, hopefully the list manager, tell me how to
> unsubscribe to this list?
>
> In attempting to sent a request for this to
>
> "[EMAIL PROTECTED]" , I got this response:
> unregister [EMAIL PROTECTED]
I think
13 matches
Mail list logo
