On Tuesday 11 February 2003 18:41, Matthew Nuzum wrote:
Can you please demonstrate the syntax you would use to create the
constraints? I'm not real clear on this and my attempts haven't
produced what I wanted.
Checked the docs? They are really good at this point. Anyways.
The following
Hello All
I was looking at this plpgsql
function:
FOR rec IN EXECUTE''select
count(person_id) as total from person where person_email like '' || $1 ||
''% and person_id IN (select cp.person_id from cluster_person cp,
cluster c where cp.cluster_id = c.cluster_id and c.c_id = '' ||
SNIP
The format of the hba.conf file changed between 7.1 and 7.2. It looks like
you are using an old one. After the database field, there is now a user
field. To get the same effect as before, use 'all' for the user.
I installed PostgreSQL rpm on a fresh installed Redhat 7.3. There is no
Tomasz Myrta wrote:
Christoph Haller wrote:
cut
Yupp, I agree.
But from former DBMS I was dealing with,
I know this SET TIMEOUT called feature, which if properly set
terminated processes like that hanging on T2.
Is there something comparable within Postgres?
PostgreSQL 7.3
Title: Message
Is there a way to add not null constraints
on a column after the column has been created? Any help would be
appreciated. Thanks.
The most likely way for the world to be destroyed, most experts agree, is by
accident. That's where we come in; we're computer professionals. We
On Tue, 11 Feb 2003, Wilkinson Charlie E wrote:
Greetings,
Can anyone enlighten me or point me at resources concerning use of pgsql
with
very large datasets?
My specific problem is this:
I have two tables, one with about 100 million rows and one with about 22,000
rows. My plan was to
