pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Re: [SQL] Column name's length
17+ messages / 5 participants
[nested] [flat]

* Re: [SQL] Column name's length
@ 1999-05-31 06:30  Zalman Stern <zalman@netcom.com>
  parent: Bruce Momjian <maillist@candle.pha.pa.us>
  0 siblings, 1 reply; 17+ messages in thread

From: Zalman Stern @ 1999-05-31 06:30 UTC (permalink / raw)
  To: maillist@candle.pha.pa.us; +Cc: tpham@mail.priority.net; pgsql-sql

I recompiled my server with support for longer (128 character max) table
names. (This was a bit tricky because you have to change things in two
places.) 32 character limits are rather low. 64 or 128 are more reasonable.
(Yes, I know this is controversial. The problem I was having is analogous
to the SERIAL problem: table names are made by concatenating together a few
fields. Each of thee fields can reasonably be 15 or 20 characters. So while
32 characters is fine for a single human generated identifier, it is not
long enough for other purposes.)

-Z-



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* column name's length
@ 1999-06-01 01:09  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 0 replies; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 01:09 UTC (permalink / raw)
  To: pgsql-sql

Hi,

Is there anyway you can increase the length of a column's name? The length
for one of my column is 21 characters and the server choke on that when i'm
trying to create the table. I'm using version 6.4.2. Below is the actual
error message i got:

postgres=> create table timeclockdepartment (
postgres-> timeclockdepartmentid serial ,
postgres-> name varchar (50) );
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or
while pr
ocessing the request.
We have lost the connection to the backend, so further processing is
impossible.
  Terminating.


I know i could have made the name much shorter, but this program was written
way before i was here and for Microsoft SQL server and i'm now trying to
move it to postgresql and encounter this problem. Thank you very much for
any reply.

-----------------
Thinh Pham
IS Manager
Priority EMS Inc.
mailto:tpham@priority.net



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Column name's length
@ 1999-06-01 01:23  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 1 reply; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 01:23 UTC (permalink / raw)
  To: pgsql-sql

Hi,

Is there anyway you can increase the length of a column's name? The length
for one of my column is 21 characters and the server choke on that when i'm
trying to create the table. I'm using version 6.4.2. Below is the actual
error message i got:

postgres=> create table timeclockdepartment (
postgres-> timeclockdepartmentid serial ,
postgres-> name varchar (50) );
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or
while pr
ocessing the request.
We have lost the connection to the backend, so further processing is
impossible.
  Terminating.


I know i could have made the name much shorter, but this program was written
way before i was here and for Microsoft SQL server and i'm now trying to
move it to postgresql and encounter this problem. Thank you very much for
any reply.

-----------------
Thinh Pham
IS Manager
Priority EMS Inc.
mailto:tpham@priority.net



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 02:41  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 1 reply; 17+ messages in thread

From: Bruce Momjian @ 1999-06-01 02:41 UTC (permalink / raw)
  To: Pham, Thinh <tpham@mail.priority.net>; +Cc: pgsql-sql

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Hi,
> 
> Is there anyway you can increase the length of a column's name? The length
> for one of my column is 21 characters and the server choke on that when i'm
> trying to create the table. I'm using version 6.4.2. Below is the actual
> error message i got:
> 
> postgres=> create table timeclockdepartment (
> postgres-> timeclockdepartmentid serial ,
> postgres-> name varchar (50) );
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or
> while pr
> ocessing the request.
> We have lost the connection to the backend, so further processing is
> impossible.
>   Terminating.


The 6.5beta error message of the same statement is:
	
	test=> create table timeclockdepartment (
	test-> timeclockdepartmentid serial ,name varchar (50) );
	ERROR:  CREATE TABLE/SERIAL implicit sequence name must be less than 32
	characters
	        Sum of lengths of 'timeclockdepartment' and
	'timeclockdepartmentid' must be less than 27

Serial creates it's own table, that is the sum of the table name and
column name.  We have not figured out a workaround for this.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 06:36  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Zalman Stern <zalman@netcom.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Bruce Momjian @ 1999-06-01 06:36 UTC (permalink / raw)
  To: Zalman Stern <zalman@netcom.com>; +Cc: tpham@mail.priority.net; pgsql-sql

> I recompiled my server with support for longer (128 character max) table
> names. (This was a bit tricky because you have to change things in two
> places.) 32 character limits are rather low. 64 or 128 are more reasonable.
> (Yes, I know this is controversial. The problem I was having is analogous
> to the SERIAL problem: table names are made by concatenating together a few
> fields. Each of thee fields can reasonably be 15 or 20 characters. So while
> 32 characters is fine for a single human generated identifier, it is not
> long enough for other purposes.)

And I assume it is working fine?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 07:33  Zalman Stern <zalman@netcom.com>
  parent: Bruce Momjian <maillist@candle.pha.pa.us>
  0 siblings, 1 reply; 17+ messages in thread

From: Zalman Stern @ 1999-06-01 07:33 UTC (permalink / raw)
  To: maillist@candle.pha.pa.us; +Cc: zalman@netcom.com; tpham@mail.priority.net; pgsql-sql

> And I assume it is working fine?

Yes. It fixes the column length too I think. The following is a psql
interaction:
-----
ssmldb=> create table
more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
(more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb boolean ) ;
CREATE
ssmldb=> select * from
more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
;
more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
---------------------------------------------
(0 rows)
ssmldb=> insert into
more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
( more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ) values ( true ) ;
INSERT 25353 1
ssmldb=> select * from
more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
;
^Mmore_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
---------------------------------------------
t
(1 row)
-----
(I did some tests to make sure all the characters are significant. They
are.)

Here are the two diffs that up the "name size" from 32 characters to 256
characters. (Once I get bit, I try to fix things real good so I don't get
bit again :-))
-----
diff  postgresql-6.4.2/src/include/postgres_ext.h postgres-build/src/include/postgres_ext.h
34c34
< #define NAMEDATALEN 32
---
> #define NAMEDATALEN 256
37c37
< #define OIDNAMELEN    36
---
> #define OIDNAMELEN    260
-----
diff postgresql-6.4.2/src/include/storage/buf_internals.h postgres-build/src/include/storage/buf_internals.h
87c87
< #define PADDED_SBUFDESC_SIZE  128
---
> #define PADDED_SBUFDESC_SIZE  1024
-----

After this, I did a clean build. I am pretty sure this produces a Postgres
that *is not* binary compatible with existing databases. You have to do the
dump/reload thing. (We discovered this issue very early on so I was able to
trash all my existing databases and start from scratch.)

I do not know what performance or space usage impact this has. If it is not
too terrible, this would be a great change to see in a future version of
Postgres.

-Z-




^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-01 13:25  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 1 reply; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 13:25 UTC (permalink / raw)
  To: pgsql-sql

Is there any reason you made OIDNAMELEN 260 instead of 256? Also, should i
wait until 6.5 came out before trying to fix this thing? Since it looks like
it's not going to be fixed in 6.5 either. I don't want to dump/reload this
thing too many times since it stores a lot of other more critical data
besides this timeclock thing. I saw the postgres website mentioned that 6.5
is coming out in around one week, is that true?
Thinh


> -----
> diff  postgresql-6.4.2/src/include/postgres_ext.h 
> postgres-build/src/include/postgres_ext.h
> 34c34
> < #define NAMEDATALEN 32
> ---
> > #define NAMEDATALEN 256
> 37c37
> < #define OIDNAMELEN    36
> ---
> > #define OIDNAMELEN    260
> -----
> diff postgresql-6.4.2/src/include/storage/buf_internals.h 
> postgres-build/src/include/storage/buf_internals.h
> 87c87
> < #define PADDED_SBUFDESC_SIZE  128
> ---
> > #define PADDED_SBUFDESC_SIZE  1024
> -----



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 14:30  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Zalman Stern <zalman@netcom.com>
  0 siblings, 0 replies; 17+ messages in thread

From: Bruce Momjian @ 1999-06-01 14:30 UTC (permalink / raw)
  To: Zalman Stern <zalman@netcom.com>; +Cc: tpham@mail.priority.net; pgsql-sql

> > And I assume it is working fine?
> 
> Yes. It fixes the column length too I think. The following is a psql
> interaction:
> -----
> ssmldb=> create table
> more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> (more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb boolean ) ;
> CREATE
> ssmldb=> select * from
> more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> ;
> more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> ---------------------------------------------
> (0 rows)
> ssmldb=> insert into
> more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> ( more_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ) values ( true ) ;
> INSERT 25353 1
> ssmldb=> select * from
> more_than_64_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> ;
> ^Mmore_than_32_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
> ---------------------------------------------
> t
> (1 row)
> -----
> (I did some tests to make sure all the characters are significant. They
> are.)
> 
> Here are the two diffs that up the "name size" from 32 characters to 256
> characters. (Once I get bit, I try to fix things real good so I don't get
> bit again :-))
> -----
> diff  postgresql-6.4.2/src/include/postgres_ext.h postgres-build/src/include/postgres_ext.h
> 34c34
> < #define NAMEDATALEN 32
> ---
> > #define NAMEDATALEN 256
> 37c37
> < #define OIDNAMELEN    36
> ---
> > #define OIDNAMELEN    260
> -----
> diff postgresql-6.4.2/src/include/storage/buf_internals.h postgres-build/src/include/storage/buf_internals.h
> 87c87
> < #define PADDED_SBUFDESC_SIZE  128
> ---
> > #define PADDED_SBUFDESC_SIZE  1024
> -----

PADDED_SBUFDESC_SIZE is gone in 6.5beta, meaning we probably now have
things tuned for NAMEDATALEN directly.

> 
> After this, I did a clean build. I am pretty sure this produces a Postgres
> that *is not* binary compatible with existing databases. You have to do the
> dump/reload thing. (We discovered this issue very early on so I was able to
> trash all my existing databases and start from scratch.)
> 
> I do not know what performance or space usage impact this has. If it is not
> too terrible, this would be a great change to see in a future version of
> Postgres.

Yes, I was thinking this too.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 14:42  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 0 replies; 17+ messages in thread

From: Bruce Momjian @ 1999-06-01 14:42 UTC (permalink / raw)
  To: Pham, Thinh <tpham@mail.priority.net>; +Cc: pgsql-sql

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Is there any reason you made OIDNAMELEN 260 instead of 256? Also, should i
> wait until 6.5 came out before trying to fix this thing? Since it looks like
> it's not going to be fixed in 6.5 either. I don't want to dump/reload this
> thing too many times since it stores a lot of other more critical data
> besides this timeclock thing. I saw the postgres website mentioned that 6.5
> is coming out in around one week, is that true?
> Thinh

It has to be 260 if NAMEDATALEN is 256:

/* OIDNAMELEN should be set to NAMEDATALEN + sizeof(Oid) */
#define OIDNAMELEN  36

6.5 is scheduled for June 7.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-01 15:45  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 2 replies; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 15:45 UTC (permalink / raw)
  To: pgsql-sql

I modified the sources as mentioned by Zalman Stern. Compiled and installed
with no problem. But when i try to connect to the database "template1" or
try to create another database, it dumped core. Below is the error message:

[postgres@ares pgsql]$ psql template1
Connection to database 'template1' failed.
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or
while processing the request.



This is when i try to create the database "postgres"

[postgres@ares pgsql]$ createdb
Connection to database 'template1' failed.
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or
while processing the request.

createdb: database creation failed on postgres.


Anyone know why this happened?
Thinh



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 16:27  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Pham, Thinh <tpham@mail.priority.net>
  1 sibling, 0 replies; 17+ messages in thread

From: Tom Lane @ 1999-06-01 16:27 UTC (permalink / raw)
  To: Pham, Thinh <tpham@mail.priority.net>; +Cc: pgsql-sql

"Pham, Thinh" <tpham@mail.priority.net> writes:
> I modified the sources as mentioned by Zalman Stern. Compiled and installed
> with no problem. But when i try to connect to the database "template1" or
> try to create another database, it dumped core. Below is the error message:

You will need to do an initdb --- you are making an incompatible change
in the format of the database.  pg_dump with old code, initdb and reload
with new.

Note that NAMEDATALEN is visible to client applications, which probably
means that libpq, psql, etc, will not interoperate across the two
different settings either.  We're talking rebuild from the ground up here.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-01 16:58  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 1 reply; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 16:58 UTC (permalink / raw)
  To: pgsql-sql

I did all of those and still it gave me that problem. What i did was
recompile the whole thing on a diff. machine/install/initdb/createdb...
still it didn't helf. Anyway, i might have to go modify the client program
instead. The only problem is this program is being used by many diff.
companies and if i modify it, and when they upgrade, they're going to have
to modify their database structure too. I just want to minimize the change
as much as possible w/o touching the frontend.

Thanks,
Thinh Pham


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, June 01, 1999 11:27 AM
To: Pham, Thinh
Cc: 'pgsql-sql@postgresql.org'
Subject: Re: [SQL] Column name's length 

You will need to do an initdb --- you are making an incompatible change
in the format of the database.  pg_dump with old code, initdb and reload
with new.

Note that NAMEDATALEN is visible to client applications, which probably
means that libpq, psql, etc, will not interoperate across the two
different settings either.  We're talking rebuild from the ground up here.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 21:31  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 1 reply; 17+ messages in thread

From: Tom Lane @ 1999-06-01 21:31 UTC (permalink / raw)
  To: Pham, Thinh <tpham@mail.priority.net>; +Cc: pgsql-sql

"Pham, Thinh" <tpham@mail.priority.net> writes:
>> You will need to do an initdb --- you are making an incompatible change
>> in the format of the database.  pg_dump with old code, initdb and reload
>> with new.

> I did all of those and still it gave me that problem.

Hmm, that probably means that Zalman hasn't found all the dependencies
on NAMEDATALEN after all :-(.  Which version are you using, exactly?

> I just want to minimize the change
> as much as possible w/o touching the frontend.

I think you missed the point I made earlier: this sort of change will
require a frontend recompile because NAMEDATALEN is visible in frontend
apps.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-01 22:05  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 0 replies; 17+ messages in thread

From: Pham, Thinh @ 1999-06-01 22:05 UTC (permalink / raw)
  To: pgsql-sql

I'm using 6.4.2. And no, i didn't miss your point about the frontend. The
frontend i'm talking about is a visual basic program running on windows, not
those programs such as psql, createdb, etc... Those are all compiled as new
since this is a new machine w/ no existing postgres installation.
Thanks, Thinh


> I just want to minimize the change
> as much as possible w/o touching the frontend.

I think you missed the point I made earlier: this sort of change will
require a frontend recompile because NAMEDATALEN is visible in frontend
apps.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* Re: [SQL] Column name's length
@ 1999-06-01 23:37  Zalman Stern <zalman@netcom.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 17+ messages in thread

From: Zalman Stern @ 1999-06-01 23:37 UTC (permalink / raw)
  To: tgl@sss.pgh.pa.us; +Cc: tpham@mail.priority.net; pgsql-sql

> Hmm, that probably means that Zalman hasn't found all the dependencies
> on NAMEDATALEN after all :-(.  Which version are you using, exactly?

I just redid my diff and the posted changes really are the only ones to my
6.4.2 sources. This database is working great on a RedHat Linux 5.2 Intel
machine. Without a stack trace from the crashing backend, there's not much
we can do from here...

I did do everything from scratch and I was seeing a crash init'ing the
database before I discovered the PADDED_SBUFDESC_SIZE dependency.

-Z-



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-02 15:38  Pham, Thinh <tpham@mail.priority.net>
  0 siblings, 0 replies; 17+ messages in thread

From: Pham, Thinh @ 1999-06-02 15:38 UTC (permalink / raw)
  To: pgsql-sql; +Cc: 'Herbert Ambos' <herbert@tuba.msuiit.edu.ph>

Hi,
I also run RH6.0. Tried the one you show down below with the NAMEDATALEN,
OIDNAMELEN, and PADDED_SBUFDESC_SIZE modifications and recompiled everything
new and it still gave me the same problem. I don't think it has anything to
do with RH6.0 because if i don't modify those three things, it worked like a
charm. Now i'm really stuck. Anyway, thank you everyone for your help.
Thinh


> -----Original Message-----
> From: Herbert Ambos [mailto:herbert@tuba.msuiit.edu.ph]
> Sent: Wednesday, June 02, 1999 8:41 PM
> To: Pham, Thinh
> Cc: 'pgsql-sql@postgresql.org'
> Subject: RE: [SQL] Column name's length
> 
> 
> 
> On Tue, 1 Jun 1999, Pham, Thinh wrote:
> 
> > ...
> >
> > [postgres@ares pgsql]$ createdb
> > Connection to database 'template1' failed.
> > pqReadData() -- backend closed the channel unexpectedly.
> >         This probably means the backend terminated 
> abnormally before or
> > while processing the request.
> > 
> > createdb: database creation failed on postgres.
> > 
> > 
> > Anyone know why this happened?
> > Thinh
> 
> this happened to me when i reinstalled my linux box into RHL6.0 and
> installing Postgres6.4.2 but i initialized my system to this:
> 
> 	initdb -l <u'r postgres lib files location (/usr/lib/pgsql)> \
>                -r <data directory (/var/lib/pgsql)>
> 
> hope this helps.?
> 
> Herbert Ambos
> Iligan City, Philippines
> 
> 



^ permalink  raw  reply  [nested|flat] 17+ messages in thread

* RE: [SQL] Column name's length
@ 1999-06-03 01:40  Herbert Ambos <herbert@tuba.msuiit.edu.ph>
  parent: Pham, Thinh <tpham@mail.priority.net>
  1 sibling, 0 replies; 17+ messages in thread

From: Herbert Ambos @ 1999-06-03 01:40 UTC (permalink / raw)
  To: Pham, Thinh <tpham@mail.priority.net>; +Cc: pgsql-sql


On Tue, 1 Jun 1999, Pham, Thinh wrote:

> ...
>
> [postgres@ares pgsql]$ createdb
> Connection to database 'template1' failed.
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or
> while processing the request.
> 
> createdb: database creation failed on postgres.
> 
> 
> Anyone know why this happened?
> Thinh

this happened to me when i reinstalled my linux box into RHL6.0 and
installing Postgres6.4.2 but i initialized my system to this:

	initdb -l <u'r postgres lib files location (/usr/lib/pgsql)> \
               -r <data directory (/var/lib/pgsql)>

hope this helps.?

Herbert Ambos
Iligan City, Philippines




^ permalink  raw  reply  [nested|flat] 17+ messages in thread


end of thread, other threads:[~1999-06-03 01:40 UTC | newest]

Thread overview: 17+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-06-01 01:09 column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-01 01:23 Column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-01 02:41 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-05-31 06:30   ` Zalman Stern <zalman@netcom.com>
1999-06-01 06:36     ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-06-01 07:33       ` Zalman Stern <zalman@netcom.com>
1999-06-01 14:30         ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-06-01 13:25 RE: [SQL] Column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-01 14:42 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-06-01 15:45 RE: [SQL] Column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-01 16:27 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-06-03 01:40 ` Herbert Ambos <herbert@tuba.msuiit.edu.ph>
1999-06-01 16:58 RE: [SQL] Column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-01 21:31 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-06-01 23:37   ` Zalman Stern <zalman@netcom.com>
1999-06-01 22:05 RE: [SQL] Column name's length Pham, Thinh <tpham@mail.priority.net>
1999-06-02 15:38 RE: [SQL] Column name's length Pham, Thinh <tpham@mail.priority.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox