-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 11 March 2004 9:11 am, Jander wrote:
> I need to abort the SQL process running in DB Server.
>
If you are in psql, you can cancel any query with CTRL-C. Otherwise, you
can kill the process running the query using the "kill" c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 27 February 2004 2:18 pm, JJ Gabor wrote:
> Hello all,
>
> I have a lookup table consisting of 100,000+ rows.
>
> 99% of the lookup values resolve to 'Unknown'.
>
> Building the lookup table takes a long time.
>
> I would like to remove the '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 26 February 2004 2:18 am, Philip J. Boonzaaier wrote:
> The technical reference gives an example of a trigger on a table -
> employee Just to test this, I have created the following table,
> CREATE TABLE employee
> (name VARCHAR(30),
> age
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 04 March 2004 9:56 am, Charles Hauser wrote:
> All,
>
> I have the following query which is running quite slow on our server
> and was hoping someone would have suggestions how I might improve it.
>
Might want to try emailing the performan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure if my original reply made it through. Ignore the last one if
it did.
On Tuesday 24 February 2004 1:48 pm, Robert Treat wrote:
> On Tue, 2004-02-24 at 12:11, Richard Huxton wrote:
> > On Tuesday 24 February 2004 16:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've written a summary of my findings on implementing and using
materialized views in PostgreSQL. I've already deployed eagerly updating
materialized views on several views in a production environment for a
company called RedWeek: http://redweek.com
