trying to do it via OUT-parameter names.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the given name and argument types. You might
need to add explicit type casts.
That doesn't sound like a type cast issue. I'd bet you connected to the
wrong database from your python app, or are using a different
search_path setting, or something along that line.
regards, tom
consider looking at contrib/pg_trgm/ to
find an indexable operation that can speed up LIKE searches.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Imre Horvath blemi...@gmail.com writes:
Is there a way to use output parameters with a pl/python fucntion?
At the moment I think plpython only supports a single OUT param.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes
think what you actually need is a transition function
that works something like
if ($1 is null)
return agg_pov_sphere($2,$3,...);
else
return concat($1, agg_pov_sphere($2,$3,...));
regards, tom lane
--
Sent via pgsql-sql
that wouldn't lead to visible
misbehavior, or why 8.4 would not like it.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
value seen by ILIKE
is just %_%, so of course it doesn't do what you want.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
return the modified row from
the trigger and let the update proceed normally.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
'::date;
?column?
--
1
(1 row)
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
*doesn't* contain a valid integer.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
, and I'd like to make
sure I'm not missing something.
You could unnest() the array and then apply the aggregate to the result.
unnest() is only built in in 8.4 and later, but it's not terribly hard
to write your own in previous versions.
regards, tom lane
--
Sent via
implementations of
en_US locale use dictionary ordering. You might prefer C locale's
rules instead.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
does not. Suggest
bugging your webhost provider to provide a less obsolete version of
Postgres.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
* from odbclink.query ...
the as business is only allowed in FROM clause.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
is this?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the hard way. Why don't you just RETURN NEW and let the
normal insertion happen?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the planner find a better plan for this query.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
from within a
SQL statement?
No. Postgres doesn't know anything about that. locale -a should work
on pretty much any Unix-ish system, but I dunno what the equivalent on
Windows would be.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org
possible this doesn't matter in this particular case
(if password can't ever be null in this table), but being careful about
nulls is a good habit to cultivate.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription
Thomas Kellerer spam_ea...@gmx.net writes:
I'm trying to get the output of the to_char(date, text) method in German but
I can't get it to work:
I think you need 'TMMon' to get a localized month name.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql
it by adjusting the
sequence parameters to prevent any caching of values.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
want to use prefix matching, don't normalize.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
to timestamptz. The
regular timestamp input converter will handle that format fine.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the right
permissions?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
there is either a bug or a version
difference here.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
*in isolation*. If you try to use it to
enforce cross-row conditions, the project will certainly end badly.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
returns no rows. NULL is NULL,
but it still has a defined datatype ...
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
$$
LANGUAGE plpgsql;
I get one row returned which is correct, but the ID column is null
(but should be 1).
Don't name the parameter the same as the table column ...
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes
as to whether inlining is legal.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Greg Stark gsst...@mit.edu writes:
On Thu, Mar 25, 2010 at 2:35 PM, Tom Lane t...@sss.pgh.pa.us wrote:
When you're intending to have a SQL function be inlined, it's probably
best not to mark it as either IMMUTABLE or STRICT --- that doesn't buy
anything and it can complicate matters
because WHERE filters rows before grouping/aggregation.
HAVING filters afterwards, which is when it makes sense to put a
condition on count(*).
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
that disabling libreadline (option -n
to psql) helps.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
other types of objects, too.)
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
exactly do you feel you need to do this every day?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
with SUSE asking for that to be added.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
There's no way that I can see to express the no cycle constraint as a
uniqueness constraint unfortunately. You could solve limited forms of
it using the exclusion-constraint mechanism that's new in 9.0, but
AFAICS not the general case :-(
regards, tom lane
--
Sent via pgsql
, maybe you could fix the
concurrency issue by taking a table-wide lock that locks out
other writers.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Richard Huxton d...@archonet.com writes:
On 16/03/10 21:09, Tom Lane wrote:
If you don't expect this to be common, maybe you could fix the
concurrency issue by taking a table-wide lock that locks out
other writers.
Surely SELECT FOR UPDATE on the parents would be sufficient? If there's
anymore.)
File an RFE, or find a more clueful distro.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
-7-bit-ASCII characters it contains?
regards, tom lane
PS: please cc the list on replies.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
for that to break anything.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
version is this anyway?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
representing the result value.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
iss.insertcitystateinfofunc();
CREATE TRIGGER update_timestamp_citystateinfo BEFORE UPDATE
ON iss.citystateinfo FOR EACH ROW
EXECUTE PROCEDURE iss.timestampfunc();
Personally I'm suspicious that the BEFORE INSERT trigger is changing the
data.
regards, tom lane
--
Sent via pgsql-sql
* from get_noobs();
ERROR: structure of query does not match function result type
DETAIL: Returned type unknown does not match expected type text in column
pass.
CONTEXT: PL/pgSQL function get_noobs line 2 at RETURN QUERY
regards, tom lane
--
Sent via pgsql-sql mailing
is normally at the front of the search path.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
into a
nextval() function call, which is why it doesn't work --- the nextval()
in the WHERE condition will produce a different value from the one in
the original INSERT. You would be far better off using a trigger here
instead of a rule.
regards, tom lane
--
Sent via pgsql
;
regression$# end$$ language plpgsql;
ERROR: missing expression at or near ;
LINE 3: return;
^
regression=#
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
message.
Postgre version on the server 8.1 on development 8.3
8.1 does not support multiple rows in a VALUES construct.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
silly sad s...@bankir.ru writes:
may i ask? when this feature will be fixed?
(now i am using 8.3.9)
The example works fine for me in 8.4.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
of the other side
of the join; repeating the scan 8 times seemed better than the
alternatives. After you improved the statistics, it most likely
switched *to* a hash join (or possibly a merge join) for this step,
rather than switching away from one.
regards, tom lane
--
Sent via
Andreas maps...@gmx.net writes:
Tom Lane schrieb:
Well, it is that --- it just doesn't provide access to all the features
that CREATE INDEX does.
So as it is a shortcut for create index then why would the function
call of upper not be accepted when the sql parser maps the
uniqe
-committers/2010-01/msg00369.php
Or, if you just need a quick workaround, use pltclu.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
in the release notes that it's now
considered unsafe.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
);
Tcl_DecrRefCount(clockObj);
if (status != TCL_OK) {
goto error2;
}
}
So apparently it's still *supposed* to work, but there's something about
the way we are using tcl that makes it not work. Any tcl experts in the
house?
regards, tom lane
--
Sent via
is that you're trying to use = NULL and
!= NULL where you should say IS NULL or IS NOT NULL.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
Yeah. As an example, overflow is supposed to be caught in a + 1,
unlike what would happen in C.
In principle you could map some of the builtin operators into inline
code, but it would be a great deal of work and the results would be
un-portable.
regards, tom lane
--
Sent
that this particular case worked before, it'd be nice if it kept
working. I'll see what I can do about it. It's too late for 8.4.2
though.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
for any output column other
than a simple column reference is implementation-dependent. I think
our implementation involves looking at the default value for a CASE.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your
likely to break existing applications
than to do anyone any good.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
= 'English, United States, UTF-8'
Not sure why you'd be expecting an English locale to follow Turkish
case-changing rules.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
forcing the issue once you've completed your data loading.
(This might involve multiple steps, which is why pg_restore
doesn't try to force it for you.)
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
, but it's probably looking for BroedselID.
Or possibly it's expecting the qualifier dbo_tbl_Broedsels.
to be included in the returned column name. Either way, you
need to bug sqldf's authors to fix it.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql
confused by that, but it works and that's what I
need.
The md5 will depend on both the actual password and the user's name
... does that help?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
(address.country).tld
to get the parser started in the right direction.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Richard Broersma richard.broer...@gmail.com writes:
Can anyone one explain why a WITH RECURSIVE query has the same
results regardless whether UNION or UNION ALL is specified?
Well, if the rows are all different anyway, UNION isn't going to
eliminate any ...
regards, tom
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
?
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
need to use regprocedure. regproc is mainly for bootstrap purposes
--- it accepts a function name only.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
... try dropping
that switch.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
,def)' ]::typ1[]);
In this case there's not much real difference, but with a lot of
array elements the individual casts get tedious.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
for its safety, considering it hasn't
been through a beta test cycle yet.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
work without, but probably
not with good performance.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the6campbells the6campbe...@gmail.com writes:
Question.. is there a way that I can get Postgres to return the tz as
supplied on the insert statement
No.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your
a date for
date '2001-03-30' - interval '1 hour'
? They are type-wise the same case; we don't have different types for
different lengths of interval.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription
and wonderful rules that embody somebody's
notion of dictionary order. If you don't like it, try switching to
C locale. Or you could learn enough about locale definitions to create
your own.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make
think you'd be best off not using a dynamically-constructed query at
all --- given the desired %'s in the LIKE pattern, there is not going
to be any benefit at all from using an unparameterized query. Just
write it out without all the string-construction.
regards, tom lane
a field to a lower level view one has to:
drop view vw_lowlevel CASCADE;
As of 8.4 you can add a column via CREATE OR REPLACE VIEW without that.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
happened and whether you're missing
anything else from the original database state ...
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
it?
That's all there is in 8.0 ...
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
the keyword will fail to process some standard-conforming
queries in a standard-conforming way.
IOW, no, we are not going to change this.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http
Jyoti Seth jyotiseth2...@gmail.com writes:
How can I disable and enable constraints in Postgres Version 8.4?
See ALTER TABLE DISABLE TRIGGER. (Fooling with reltriggers has been
deprecated since 8.1.)
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql
can this operation
be altered?
Get rid of long-running transactions that hold locks on the contexts
table.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
rawi only4...@web.de writes:
Grails/Hibernate wishes per default one sequence for all tables-PKs and all
PKs as BigInt.
Redesign that software; this is fundamentally broken and stupid.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org
that isn't available to user-written constraints.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Gerardo Herzig gher...@fmed.uba.ar writes:
Obviously im missing something, i cant find any relation between
pg_proc.pronamespace and pg_namespace.
You didn't look at pg_namespace.oid, which is a system column
meaning SELECT * doesn't show it.
regards, tom lane
--
Sent
to the sub-select to keep the planner from
flattening the sub-select and producing multiple calls of the function.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Pavel Stehule pavel.steh...@gmail.com writes:
COPY in plpgsql are not allowed.
I think it will work if you use an EXECUTE.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
... WHERE id = ANY(string_to_array('1,3,7,8', ',')::int[]) ...
Of course this just begs the question of why the OP doesn't use an
array in the first place.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription
101 - 200 of 2222 matches
Mail list logo
