Eric Worden wrote:
> The recursive function creates a temp table [...] I
> have version 8.1.10.
While I haven't looked in detail, I'd be surprised if this wasn't an
issue with pre-8.3 versions lack of any way to automatically re-generate
cached plans in functions.
Try running your code on an 8.
On Fri, 26 Dec 2008 19:13:48 -0500
Tom Lane wrote:
> The subselect syntax certainly seems like the one most likely to
> work across different SQL implementations. WITH is a pretty
subselects actually works on mysql too but on a 1M table with about
300K unique columns it performs more than 4 tim
Andrej Podzimek wrote:
> "The files server.key, server.crt, root.crt, and root.crl are only
> examined during server start; so you must restart the server for
> changes in them to take effect."
> (http://www.postgresql.org/docs/8.3/static/ssl-tcp.html)
>
> This is perfectly fine for server.key, se
I have a table, queries, with a column value. There is a trigger on
this table that inserts into query_history for each update to value.
I'm trying to graph the query_history table, so I was using a custom
aggregate to turn it into an array:
CREATE AGGREGATE array_accum (anyelement)
(
sfunc = arr
"Jeffrey Melloy" writes:
> It seems like I should be able to order by quer_time desc and then
> query_time asc. Am I missing something?
You'd have to do it *after* the join and GROUP BY if you want it to
control the input to the aggregate reliably. Either of those operations
will feel free to ou
I'm aware that if you create a foreign key constraint, no indexes are
automatically created.
I would like to find a way to programatically inspect all my foreign keys and
identify possibly missing indexes on either table (either the table defining
the constraint or the table being referenced).
