Dragan Matic <[EMAIL PROTECTED]> writes:
> create table sample(column_sample varchar(500))
> insert into sample(column_sample) values('this is first row of text' ||
> chr(10) || 'this is second row of text')
> Now, instead of just inserting chr(10), postgres inserts chr(13) +
> chr(10).
Postgres most certainly does not do that, as even a moment's
experimentation (eg, with length()) will prove to you. Take a closer
look at your client-side software to find out where the newline
conversion is happening.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
