On Thu, May 29, 2008 at 9:45 PM, Theerasak Maneeneim
<[EMAIL PROTECTED]> wrote:
> Dear All,
>
> I have some problem with string comparison. I use postgresql
> 8.3.1,UTF8 encoding, on CentOS 5.5. Why dose the result of SQL statement :
> "select '1.1' < '101';" is false but "select '1.1':
Dear All,
I have some problem with string comparison. I use
postgresql 8.3.1,UTF8 encoding, on CentOS 5.5. Why dose the result of
SQL statement : "select '1.1' < '101';" is false but "select
'1.1'::bytea < '101'::bytea;" is ture?
mis=# select '.' < '0';
?column?
--
t
(1
Emi Lu wrote:
...
I have a table from around 10 million to 90,000, after deletion, I
tried to use vacuum full, but it seems that it takes forever to
finish. Could anyone tell me how long it will take to finish the
Recovering disk space please?
No. Probably a lonng time.
In a case lik
On Thu, May 29, 2008 at 11:33:36AM -0400, Emi Lu wrote:
> I have a table from around 10 million to 90,000, after deletion, I tried to
> use vacuum full, but it seems that it takes forever to finish. Could anyone
> tell me how long it will take to finish the Recovering disk space please?
A reall
Good morning,
A question about VACUUM FULL. The docs say:
VACUUM FULL is recommended for cases where you know you have deleted the
majority of rows in a table, so that the steady-state size of the table
can be shrunk substantially with VACUUM FULL's more aggressive approach.
Use plain VACUUM,
