On Wed, Feb 25, 2009 at 10:50 PM, Ashish Karalkar
wrote:
> manoj selukar wrote:
>>
>> Hi all,
>>
>> I am very happy to join with u! and thanks to all being helpful,
>>
>> I am totally new for this admin work ,So i would like to know the main
>> work to be done, what type of operation should i do,a
manoj selukar wrote:
Hi all,
I am very happy to join with u! and thanks to all being helpful,
I am totally new for this admin work ,So i would like to know the main
work to be done, what type of operation should i do,and learn that are
important for admin.
Thanks!
Manoj
This should sta
Hi all,
I am very happy to join with u! and thanks to all being helpful,
I am totally new for this admin work ,So i would like to know the main work
to be done, what type of operation should i do,and learn that are important
for admin.
Thanks!
Manoj
hi Harald,
I reboot the machine and create index,it works.thanks.
2009/2/26 Harald Fuchs
> In article <8f750b7c0902250259w6065515as350aca3b5d7d8...@mail.gmail.com>,
> Tony Liao writes:
>
> > hi all,
> > I have a table table_A (id serial,prefix varchar),for example.
> > now I w
thanks,everybody!
Harald,you understand correctly.I downloaded the prefix contrib
and install,by the way,it seems that the prefix has bugs,I had to modify the
Makefile and then install success.
and then,I imported the prefix.sql.I did a test,but I found I
can't create index of
Avi Blackmore wrote:
Hi folks,
I'm working on migrating our database cluster from PostgreSQL 8.1 to
8.3. I'm following the "dump and restore, then use Slony to
replicate" procedure, to minimize downtime. The problem is, the new
2.0 version of Slony-I does not support anything prior to 8
"Daniel J. Summers" writes:
> MySQL will only use it if the wildcard isn't in the front (1) and
> requires the MATCH keyword to search full-text indexes (2), Oracle
> requires special "full-text" indexes to be able to use for LIKE (3)
> (actually dealt with that at work a few months back), SQL
Andrzej Zawadzki wrote:
Daniel J. Summers wrote:
Tony Liao wrote:
I try to explain analyze,but it doesn't work ,it use seq scan.
Generally speaking, LIKE doesn't use indexes.
?! That's not true at all!!
MySQL will only use it if the wildcard isn't in the front (1) and
Isabella Ghiurea writes:
> My concern is after a PG upgrade to 8.3.6 the psql behavior has been
> changed : can't use history line anymore .
Apparently you failed to build it with readline support. The correct
response is to fix that; no amount of fooling with psqlrc files will
help.
My concern is after a PG upgrade to 8.3.6 the psql behavior has been
changed : can't use history line anymore .
The updates to .psql_history file has been stopped after upgrade, so I
was looking to create my own psqlrc file.
Note : PG upgrade has been installed using the tarball file ( sou
On Wed, Feb 25, 2009 at 3:20 PM, Avi Blackmore wrote:
> Hi folks,
>
> I'm working on migrating our database cluster from PostgreSQL 8.1 to 8.3.
> I'm following the "dump and restore, then use Slony to replicate"
> procedure, to minimize downtime. The problem is, the new 2.0 version of
> Slony-I
Hi folks,
I'm working on migrating our database cluster from PostgreSQL 8.1 to
8.3. I'm following the "dump and restore, then use Slony to
replicate" procedure, to minimize downtime. The problem is, the new
2.0 version of Slony-I does not support anything prior to 8.3, so I
have
On Tue, Feb 24, 2009 at 9:51 PM, Isabella Ghiurea <
isabella.ghiu...@nrc-cnrc.gc.ca> wrote:
> I have installed pg 8.3.6 from source code and I want to configure the
> psqlrc file , BUT can't find to much tips and documentation:
> Can anyone provide a good working copy here and the location/path wh
Daniel J. Summers wrote:
> Tony Liao wrote:
>> I try to explain analyze,but it doesn't work ,it use seq scan.
> Generally speaking, LIKE doesn't use indexes.
?! That's not true at all!!
--
Andrzej Zawadzki
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
In article <8f750b7c0902250259w6065515as350aca3b5d7d8...@mail.gmail.com>,
Tony Liao writes:
> hi all,
> I have a table table_A (id serial,prefix varchar),for example.
> now I want to get the id of "johnsmith"'s prefix match table_A.prefix,so
> I do select id from table_A where 'johnsm
Hi Lee, just got your reply.
Every segment comes over compressed (gzip). So every segment would be a
Different size in the compressed folder. But we decompress it into another
folder (gzip) and they always decompress into the standard 16 meg size when
We copy them back into xlog.
So 00010
Is 00010C2800B1 the same size as the other segments?
-lee
2009/2/25 Mark Steben :
> Hi listers,
>
>
>
> Here is my problem. I am running PITR restore on a machine remote from my
> production machine.
>
> I'm shipping logs over there, compressed, then uncompressing them and
> copying
Hi listers,
Here is my problem. I am running PITR restore on a machine remote from my
production machine.
I'm shipping logs over there, compressed, then uncompressing them and
copying them to pg_xlog.
Everything works fine until a network outage creates a gap in my logs.
The recovery termin
Tony Liao wrote:
I try to explain analyze,but it doesn't work ,it use seq scan.
Generally speaking, LIKE doesn't use indexes. However, there are a
couple of things you could try - definitely use EXPLAIN to see if this
gets you the improvement you're looking for.
- You could try using = on the
2009/2/25 Michael Monnerie
> On Mittwoch 25 Februar 2009 Tony Liao wrote:
> > hi all,
> > I have a table table_A (id serial,prefix varchar),for example.
> > now I want to get the id of "johnsmith"'s prefix match
> > table_A.prefix,so I do select id from table_A where 'johnsmith' like
On Mittwoch 25 Februar 2009 Tony Liao wrote:
> hi all,
> I have a table table_A (id serial,prefix varchar),for example.
> now I want to get the id of "johnsmith"'s prefix match
> table_A.prefix,so I do select id from table_A where 'johnsmith' like
> prefix||'%'
SELECT id FROM table_A
hi all,
I have a table table_A (id serial,prefix varchar),for example.
now I want to get the id of "johnsmith"'s prefix match
table_A.prefix,so I do select id from table_A where 'johnsmith' like
prefix||'%' ,the table_A is very large so I would like to make index.
create table_A_index
Hello ML,
I'm very new to Postgres.
In the log, i got messages concerning transaction ID wraparound.
I red the documentation and made a vaccum on that database.
In the documentation i also found the hint to look in the database with
"SELECT datname, age(datfrozenxid) FROM pg_database;", which i di
23 matches
Mail list logo
