Unix Technical Forum

SEO

vBulletin Search Engine Optimization


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > Pgsql General

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 05-10-2008, 02:04 PM
Christian.Strobl@dlr.de
 
Posts: n/a
Default reproducible database crash with simple sql command on postgres 8.3.1


hi all,

first i create a table
create table regions (id integer, name varchar);

then i want to set a default value for a column, e.g.
alter table regions alter column name set default 'bavaria';

at this point crashes the database with the message

PANIK: ERROR_STACK_SIZE exceeded

the rest of the message is unfortunately in german then i have to
restart the postgres-service manually this error is very easy
reproducible at my environment

is this a problem of my installation or can anybody reproduce this error
at his environment

thanks and greetings from munich
christian

p.s. os windows xp, sp2
postgres 8.3.1, visual c++, build 1400

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 05-10-2008, 02:04 PM
josep porres
 
Posts: n/a
Default Re: reproducible database crash with simple sql command on postgres 8.3.1

No problems here.


create table regions (id integer, name varchar);
alter table regions alter column name set default 'bavaria';


PostgreSQL 8.3.1 vc++ build 1400 xp sp2

# - Memory -

shared_buffers = 32MB # min 128kB or max_connections*16kB
# (change requires restart)
#temp_buffers = 8MB # min 800kB
temp_buffers = 8MB # min 800kB

#max_prepared_transactions = 5 # can be 0 or more
# (change requires restart)
# Note: Increasing max_prepared_transactions costs ~600 bytes of shared
memory
# per transaction slot, plus lock space (see max_locks_per_transaction).
#work_mem = 1MB # min 64kB
work_mem = 2MB # min 64kB
#maintenance_work_mem = 16MB # min 1MB
maintenance_work_mem = 32MB # min 1MB
max_stack_depth = 2MB # min 100kB




cheers


Josep


2008/5/9 <Christian.Strobl@dlr.de>:

>
> hi all,
>
> first i create a table
> create table regions (id integer, name varchar);
>
> then i want to set a default value for a column, e.g.
> alter table regions alter column name set default 'bavaria';
>
> at this point crashes the database with the message
>
> PANIK: ERROR_STACK_SIZE exceeded
>
> the rest of the message is unfortunately in german then i have to
> restart the postgres-service manually this error is very easy
> reproducible at my environment
>
> is this a problem of my installation or can anybody reproduce this error
> at his environment
>
> thanks and greetings from munich
> christian
>
> p.s. os windows xp, sp2
> postgres 8.3.1, visual c++, build 1400
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 05-10-2008, 02:04 PM
Tom Lane
 
Posts: n/a
Default Re: reproducible database crash with simple sql command on postgres 8.3.1

<Christian.Strobl@dlr.de> writes:
> PANIK: ERROR_STACK_SIZE exceeded


> the rest of the message is unfortunately in german then i have to
> restart the postgres-service manually this error is very easy
> reproducible at my environment


What this typically means is that you've got an encoding/locale
configuration problem. The thing is trying to report some error
or other, and it discovers that the error text is badly encoded
according to the current database encoding, and it tries to
report that, only *that* error text is badly encoded too, so
it tries to report that, getting another error, etc, until the
error recovery stack overflows.

The hope of getting rid of this scenario is one reason why we locked
down encoding/locale combinations in 8.3, so I'm disappointed that
you're still able to make it happen. You didn't say what settings
you are using though. Could we see

show lc_messages;
show lc_ctype;
show server_encoding;
show client_encoding;

regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 04:41 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145