Search Postgresql Archives

Re: There can be only one! How to avoid the "highlander-problem".

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: There can be only one! How to avoid the "highlander-problem".
From: Erwin Brandstetter <brsaweda@xxxxxxxxx>
Date: Sat, 02 Jun 2007 09:39:47 -0700
Complaints-to: groups-abuse@xxxxxxxxxx
In-reply-to: <4660BD3A.7000603@xxxxxxxxx>
Injection-info: u30g2000hsc.googlegroups.com; posting-host=80.109.13.165; posting-account=motVOw0AAAAl5BtLWL3QN4EcB1CKG8U3
Organization: http://groups.google.com
References: <4660BADB.2010403@xxxxxxxxx><4660BD3A.7000603@xxxxxxxxx>
User-agent: G2/1.0

On Jun 2, 2:43 am, brandstet...@xxxxxxxxx (Erwin Brandstetter) wrote:
>   raise warning '%', kings;

And remove this line of debug code.

/Erwin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: There can be only one! How to avoid the "highlander-problem".
  - From: Lew

References:
- There can be only one! How to avoid the "highlander-problem".
  - From: Erwin Brandstetter
- Re: There can be only one! How to avoid the "highlander-problem".
  - From: Erwin Brandstetter

Prev by Date: Re: Transactional DDL
Next by Date: Re: Transactional DDL
Previous by thread: Re: There can be only one! How to avoid the "highlander-problem".
Next by thread: Re: There can be only one! How to avoid the "highlander-problem".
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux