Re: pg full text search very slow for Chinese characters

Hi. At Tue, 10 Sep 2019 18:42:26 +0200 (CEST), Andreas Joseph Krogh wrote in > På tirsdag 10. september 2019 kl. 18:21:45, skrev Tom Lane > >: Jimmy Huang writes: > > I tried pg_trgm and my own customized token parser > https://github.com/huangjimmy/pg_cjk_parse

Re: kind of a bag of attributes in a DB . . .

On 9/10/19 9:59 AM, Albretch Mueller wrote: On 9/7/19, Adrian Klaver wrote: Is the metadata uniform or are you dealing with a variety of different data? You can expect for all files to have a filename and size, but their kinds (the metadata describing them) can be really colorful and wild w

Recover data from aborted transactions

I've used PITR on a number of occasions to look back at old data and recover deleted records. Recently while searching for a missing record I ran across the following line in the output of pg_xlogdump: rmgr: Transaction len (rec/tot):200/ 226, tx: 26025438, lsn: > 127/9166CF18, prev 127/91

Re: kind of a bag of attributes in a DB . . .

On 9/7/19, Adrian Klaver wrote: > Is the metadata uniform or are you dealing with a variety of different > data? You can expect for all files to have a filename and size, but their kinds (the metadata describing them) can be really colorful and wild when it comes to formatting. lbrtchx

Re: pg full text search very slow for Chinese characters

På tirsdag 10. september 2019 kl. 18:21:45, skrev Tom Lane mailto:t...@sss.pgh.pa.us>>: Jimmy Huang writes: > I tried pg_trgm and my own customized token parser https://github.com/huangjimmy/pg_cjk_parser pg_trgm is going to be fairly useless for indexing text that's mostly multibyte characte

Re: pg full text search very slow for Chinese characters

Jimmy Huang writes: > I tried pg_trgm and my own customized token parser > https://github.com/huangjimmy/pg_cjk_parser pg_trgm is going to be fairly useless for indexing text that's mostly multibyte characters, since its unit of indexable data is just 3 bytes (not characters). I don't know of a

Re: pg full text search very slow for Chinese characters

It is all default values. I just check maintenance_work_mem and indeed it is 64MB. At first I gave 2GB ram to docker and later I increased ram to 4GB. It did not make much difference when ram increased from 2GB to 4GB. I will try increasing maintenance_work_mem and see if it helps. 发件人: Michael

Re: pg full text search very slow for Chinese characters

On Tue, Sep 10, 2019 at 10:11 AM Michael Lewis wrote: > >My postgres instance is based on docker image postgres:11 and runs on my > MacBook Pro i7 16GB. > > How much ram and such did you give to this vm? > > > >To my surprise, postgres 11 is extremely slow when creating a full text > index. I add

Re: pg full text search very slow for Chinese characters

>My postgres instance is based on docker image postgres:11 and runs on my MacBook Pro i7 16GB. How much ram and such did you give to this vm? >To my surprise, postgres 11 is extremely slow when creating a full text index. I added a column of tsvector type and tried to create an index on that col

Re: pg full text search very slow for Chinese characters

Well, there is a lot of information we would need to diagnose this. How much tuning have you done?, etc. My advice is pretty simple. Don't expect performance on a notebook and, unless you are planning on hosting it on a notebook, use the notebook for development only . Test performance on a pro

pg full text search very slow for Chinese characters

Hi Team, Can anyone shed some light on why postgres 11 is extremely slow in my case? I am making a mirror of zh.wikisource.org and I have downloaded 303049 pages and stored them in a postgres 11 database. My postgres instance is based on docker image postgres:11 and runs on my MacBook Pro i7 1

Re: pgrounting extension in 11

Thanks, I'll check it out. On Tue, Sep 10, 2019, 19:49 Adrian Klaver wrote: > On 9/10/19 6:53 AM, Prakash Ramakrishnan wrote: > > Hi Adrian, > > > > I have only these files in pgdg, > > That is something you will need to take up with the PGDG RH packagers. > You can file an issue here: > > https

Re: pgrounting extension in 11

On 9/10/19 6:53 AM, Prakash Ramakrishnan wrote: Hi Adrian, I have only these files in pgdg, That is something you will need to take up with the PGDG RH packagers. You can file an issue here: https://redmine.postgresql.org/projects/pgrpms/issues?set_filter=1 NOTE: You will a need a Postgres

Re: pgrounting extension in 11

Hi Adrian, I have only these files in pgdg, [root@hkgrhepdbp001 ~]# yum list | grep pgrouting This system is not registered with RHN Classic or RHN Satellite. You can use rhn_register to register. RHN Satellite or RHN Classic support will be disabled. pgrouting_93.x86_642.0.0-

Re: pgrounting extension in 11

On 9/10/19 5:59 AM, Prakash Ramakrishnan wrote: Hi Team, Anyone help me to solve the below issue not able to create the pgrouting extension 11 version in rhel 6.9 OS, What repo's are you pulling from RH's or PGDG? If PGDG then I do not see pgRouting for RH 6.x: https://yum.postgresql.org/te

pgrounting extension in 11

Hi Team, Anyone help me to solve the below issue not able to create the pgrouting extension 11 version in rhel 6.9 OS, [root@hkgrhepdbp001 ~]# yum install pgrouting_11 Loaded plugins: enabled_repos_upload, package_upload, product-id, rhnplugin, search-disabled-repos, security, subscription-manag