Re: sudden program termination: no warning, error, or crash

Hi.

Um, sorry, I can't reproduce a problem....
If possible, please send me the script which can reproduce a problem.

Regards,
Hiroshi Saito

----- Original Message -----
From: "Dave Page" <dpage(at)pgadmin(dot)org>

On Thu, Aug 20, 2009 at 12:41 AM, JwexlerAt
MailDotCom<jwexler(at)mail(dot)usa(dot)com> wrote:
> The error often happens after I have created a number of columns and then creating the two
> timestamp with timezone columns at which the error seams to appear most. Naming convention is
> lower case first word, then capital first character of subsequent words. Table creation is
> generally as such (toggling between Excel 2007 and pgAdminIII at every step (I use the Excel
> datamodel to manage the design/changes/planning etc of the db due to the inability of PostgreSQL
> to allow for easily re-order positions of columns as well as some other reasons).
> * Create table
> * Create a bigserial, non-null column called "serialNumInt" (This is the primary key on all
> tables with the exception of many-to-many tables)
> * Create a text column called "recordDescriptiveCodeStr". Add a comment to it after creation.
> * On many-to-many tables, create two bigint, non-null columns. Then make them jointly the primary
> key. Add separate foreign keys to each (using the default settings for the foreign keys). Add a
> comment to some of them after creation.
> * Add a bigint column, null ok. Add a foreign key for this column (using default settings for the
> foreign key).
> * Create various text, bigint, and double precision columns (depending on the table)
> * Create 3 text columns
> * Create a bigint column
> * Create the two "timestamp with time zone" columns. Each have a comment (6 words for the first
> one, 7 words for the second one).
> The termination is intermittent. Usually, there is no termination. When there is one, it seems
> most often during the creation of the second "timestamp with time zone" column (i.e., the last
> column of the table).

What encoding/locale is your database using?

Hiroshi/Quan - are either of you able to reproduce this issue? I'm
wondering if this is something specific to Japanese Windows/locales
etc.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com