Jim C. Nasby mentioned :
=> Are you seeing much gain using ztext over using EXTENDED?
When storage is defined external, there is a visible gain,
but not really significant enough to make me want to use it.
And I had instances where not all the rows would uncompress again
afterwards. I want to tr
On Mon, Oct 10, 2005 at 02:18:39PM +0200, Stef wrote:
> I have a table in the databases I work with,
> that contains two text columns with XML data
> stored inside them.
>
> This table is by far the biggest table in the databases,
> and the text columns use up the most space.
> I saw that the de
Thanks, after playing around a little I found that placing the indices
on a different drive gave a real performance increase in my scenario.
Johann
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Monday, October 10, 2005 4:35 PM
To: Weber, Johann (ISS Kassel)
Cc: pgsql
"Weber, Johann (ISS Kassel)" <[EMAIL PROTECTED]> writes:
> Is this true for PostgreSQL (V 8.0 on ReadHat)? My tests do not show any
> speed gained when placing pg_clog and pg_xlog on a different drive.
The conventional wisdom is that it's a win to have pg_xlog on a drive by
itself. The above is n
Gary Stainburn <[EMAIL PROTECTED]> writes:
> I've done a pg_dumpall and then imported that to the new system but a
> copy is failing with the following:
> psql:/backups/eddie_pg_dumpall.sql:3076: ERROR: invalid input syntax
> for type money: "£3.18"
> CONTEXT: COPY invoices, line 1, column net
Hannes Dorbath <[EMAIL PROTECTED]> writes:
> On 10.10.2005 11:56, Luca Ferrari wrote:
>> gestione_personale=# \l
>> List of databases
>> Name| Owner | Encoding
>> +---+---
>> gestione_database | dbmanager | SQL_ASCII
>> gestione_personale | wwwrun
On Mon, Oct 10, 2005 at 03:20:47PM +0500, M. Imran wrote:
> I want to select distinct CODE and thier respective sex, sex can
> be male/female, can I get my result strictly distinct in code.
> Currently it duplicate code value for each male and female. I am
> using this query
>
> select distinct(c
On 10.10.2005 14:24, Luca Ferrari wrote:
The old rows are still displayed in a bad format, the newly inserted one
is instead shown rightly. Also data in pg_dump present wrong strings,
thus any suggestion about how to reconvert already inserted data?
It should be possible to convert it with an
Hannes Dorbath's cat, on 10/10/2005 12.08, walking on the keyboard wrote:
OK, so you are not using Unicode. I don't know much about the SQL_ASCII
charset, but I expect it to slightly differ from LATIN1. Type
SET client_encoding = LATIN1;
in psql, then SELECT some data containing the chars you
I have a table in the databases I work with,
that contains two text columns with XML data
stored inside them.
This table is by far the biggest table in the databases,
and the text columns use up the most space.
I saw that the default storage type for text columns is
"EXTENDED" which, according t
It /MAY/ help to use a newer pg_dump / pg_restore binary with -i option.
Try to dump and restore using 8.1 binaries for example.
On 10.10.2005 13:25, Gary Stainburn wrote:
I'm trying to move an existing setup on a 7.2 system to another existing
box running 7.4.
I've done a pg_dumpall and the
..and I guess using custom format (-F c -Z 9) might be saver, because a
newer pg_restore binary then might have a chance to correct things,
depending on the server version it is used against.
On 10.10.2005 13:25, Gary Stainburn wrote:
I'm trying to move an existing setup on a 7.2 system to anot
I learned for other
database systems, that it is an advantage to have database on one physical drive
and transaction logs on a different physical drive, as this should minimize
seeks on the hard-disks.
Is this true for
PostgreSQL (V 8.0 on ReadHat)? My tests do not show any speed gained wh
Hi folks.
I'm trying to move an existing setup on a 7.2 system to another existing
box running 7.4.
I've done a pg_dumpall and then imported that to the new system but a
copy is failing with the following:
psql:/backups/eddie_pg_dumpall.sql:3076: ERROR: invalid input syntax
for type money:
On 10.10.2005 11:56, Luca Ferrari wrote:
gestione_personale=# \l
List of databases
Name| Owner | Encoding
+---+---
gestione_database | dbmanager | SQL_ASCII
gestione_personale | wwwrun| SQL_ASCII
template0 | dbm
Dear all,
I want to select
distinct CODE and thier respective sex, sex can be
male/female, can I get my result strictly distinct in code. Currently
it duplicate code value for each male and female. I am using this query
select distinct(code), id from
table
Regards,
imran
On 10.10.2005 10:34, Luca Ferrari wrote:
Do you mean dumping the database, destroying it and then recreating it?
I'm sorry, but I'm still new in postgresql, thus it is not clear if
meant that or another trick I don't know.
Let us find the problem before jumping to solutions. Start psql
, typ
Hannes Dorbath's cat, on 10/10/2005 9.28, walking on the keyboard wrote:
The client encoding can be set anytime, to change the cluster LOCALE or
database encoding you need to initDB + dump and restore AFAIK.
Do you mean dumping the database, destroying it and then recreating it?
I'm sorry, but
like "èòéàùì", the string is stored in the database with other characters
instead of those digited by the user.
Well, how does `èòéàùì' look like in your database? Like `èòéà ùì'?
In that case you most probably have initialized your cluster with an
UTF-8 locale while not using a / the co
19 matches
Mail list logo
