Re: reproducible database crash with simple sql command on postgres 8.3.1
От | josep porres |
---|---|
Тема | Re: reproducible database crash with simple sql command on postgres 8.3.1 |
Дата | |
Msg-id | d2d532610805090241r4a66076cwc8af1306cc2c3934@mail.gmail.com обсуждение исходный текст |
Ответ на | reproducible database crash with simple sql command on postgres 8.3.1 (<Christian.Strobl@dlr.de>) |
Список | pgsql-general |
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
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
В списке pgsql-general по дате отправления: