It appears that the Slony list isn't accepting traffic/posts at all. I
posted a message yesterday (2004-08-24) and haven't even received it
myself at this point (2004-08-25). Just thought I'd give a heads up, in
case now one knew.
---(end of
If I'm not mistaken you have an infinit recursion because you are always
pulling the same id (whatever _id starts at) throughout each function call.
Postgres is most likely killing the functions when it's hits some stack
or memory limit.
Mark Cave-Ayland wrote:
Hi everyone,
I'm trying to write
I've never used dblink, but why don't you store your connection strings
in a table.
CREATE connections (id SERIAL PRIMARY KEY, conn_str text NOT NULL);
The create a function as SECURITY DEFINER that takes id as a parameter
and returns the conn_str
CREATE OR REPLACE FUNCTION get_connection(INT)
No you cannot.
But look at this for a pointer:
select 'hi' || (select substring('hello1234567890' from '[0-9]+$'))
where 'hello1234567890' ~* '[a-z]+([0-9+])';
CSN wrote:
Can you use backreferences in regular expressions like
so?
update table set title='foobar ' || \1 where title ~*
Just dropping a quick not for Tom Lane. I sent a personal message
today, but I wasn't sure if you'd get it after I remembered all of the
spam filters you've got set up.
Sorry for the off topic post.
---(end of broadcast)---
TIP 5: Have you
B. van Ouwerkerk wrote:
IMO there's no valid reason for MySQL bashing. I'm not going to defend
either one because that kind of discussion leads to nowhere.
How about pure entertainment? Or maybe because we don't have anything
better to do on a Friday night because the one girl this year who
The queries are listed here for the referentially (yes that's a pun)
challenged.
Query 1:
SELECT COUNT(message_id)
FROM messages m
LEFT JOIN accounts a
ON m.account_id::bigint = a.account_id::bigint
WHERE a.email = '[EMAIL PROTECTED]';
Query 2:
SELECT COUNT(message_id)
FROM accounts
Why not place the pid of the process into your session and set up a
cronjob to look at pg_listner and delete any pid's from the session
file that have gone away? Only down side is if you recycle pid's
really quickly.
Alvaro Herrera wrote:
On Fri, Nov 07, 2003 at 07:33:47PM -0800, Boris
quick answer: research/read the pg_hba.conf in the data directory.
Jeff MacDonald wrote:
Hi,
WHen i run pg_dumpall as the super user [postgres in my case] it asks
for a password for every database. I don't know my users passwords. Is
there a way to make the super user able to backup without
Gagan Anand wrote:
Hello,
i have data in form of images which are in GB's,
i need to store the extracted data from the images.
This will required large fields size.
I was thinking of Blob data type as we have in
Oracle. Do we have blob data type in postgreSQL, if
yes in which version.
So I have a query in which some of the select values are
subqueries. The
subqueries are aggregates so I don't want to turn this into a join,
it would
become too complex and postgres would have trouble optimizing things.
So my question is, is there some way to have a subselect return
multiple
size as all the others combined).
Joshua D. Drake wrote:
Hello,
Why in the world would you want to do this? It seems that there
should be a better way.
Sincerely,
Joshua Drake
DeJuan Jackson wrote:
Does anyone know how to execute a COPY from PHP?
I keep getting parse errors on all the data
people use RH8 on
multiprocesor boxes, and it works great!
Jon
On Wed, 6 Aug 2003, DeJuan Jackson wrote:
Don't know the answer to your question, but I thought I would just pipe
in and say that if this is an SMP (has multiple processors) Linux box
you don't want to use ext3!!!
I used ext3 on my
use a sub-select
SELECT SUM(volume)
FROM (SELECT volumn FROM tablename
WHERE element = 'name1' ORDER BY date DESC LIMIT 30) t
Castle, Lindsay wrote:
Hi All,
A quick select query I'm having some dramas with;
I'm trying to SUM a number of values based on them being the latest entries
based on
Assuming you have done a 'VACUUM ANALYZE' on the table in question you
are most likely running into a type coercion issue.
So explicitly cast your constants to bigint and the index should start
being considered.
select id from table where col2 = 1::bigint and col2 = 1::bigint
Tim McAuley
Ron Johnson wrote:
On Wed, 2003-07-30 at 09:25, scott.marlowe wrote:
On Wed, 30 Jul 2003, Gogulus wrote:
As the clients should be able to work without network connection, they
have to have a local database, and if net connection is on, do the
synchronization
Rory Campbell-Lange wrote:
I have been informed that at present (postgres 7.3.2) using IN is not
advised, and I should replace it with EXISTS. I can't seem to get it to
work.
I've tried replacing (example):
SELECT
name
FROM
people
WHERE
state IN (
SELECT
Just wondering (I don't use or intend to use plpython), but why does it
need to be marked untrusted is the rexec code has been corrected.
Bruce Momjian wrote:
Patch applied. Thanks.
---
Kevin Jacobs wrote:
18 matches
Mail list logo