| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
| Cc: | pggeneral <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: name truncation problem in 7.0.0 |
| Date: | 2001-05-11 19:51:59 |
| Message-ID: | 6699.989610719@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ed Loehr <eloehr(at)austin(dot)rr(dot)com> writes:
> Maybe someone can confirm what looks like a long-name-truncation bug in
> 7.0.0?
I see no bug here; it told you what name it planned to use for the
sequence:
> psql:/home/ed/pgbug:8: NOTICE: CREATE TABLE will create implicit
> sequence 'process_state_subscripti_id_seq' for SERIAL column
> 'process_state_subscription.id'
so this is not surprising:
> DROP SEQUENCE process_state_subscription_id_seq;
> psql:/home/ed/pgbug:10: NOTICE: identifier
> "process_state_subscription_id_seq" will be truncated to
> "process_state_subscription_id_s"
> psql:/home/ed/pgbug:10: ERROR: Relation
> 'process_state_subscription_id_s' does not exist
It's not a bug that the sequence name is formed with a rule more complex
than "truncate table_field_seq at the right" ... if we did that, you'd
have a problem with sequences for tables with names longer than 32
characters ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2001-05-11 20:05:55 | Re: PL/Perl without shared libperl.a |
| Previous Message | Tom Lane | 2001-05-11 19:45:19 | Re: Index on a function(field) |