| -- List running queries | |
| -- | |
| select query,* from pg_stat_activity; | |
| -- Show cache hit ratio | |
| -- | |
| SELECT | |
| sum(heap_blks_read) as heap_read, | |
| sum(heap_blks_hit) as heap_hit, | |
| sum(heap_blks_hit) / (sum(heap_blks_hit) + sum(heap_blks_read)) as cache_hit_ratio |
Here is a regular expression I created to identify Capitalized and ALLCAPS alphanumeric words that are not at the start of a sentence which may indicate they are proper names aka a pronoun. It uses a lookbehind ?<= to avoid matching words at the start of a sentence.
(?<=[\w,:;-])\s+([A-Z0-9]+[A-Za-z][A-Za-z0-9]*)\b
See it working at the handy website Regex101 - https://regex101.com/r/5haqtp/2
| Verifying my Blockstack ID is secured with the address 156EHDsWbvkWaHbhRXMCBRqkwQY31kfNLc https://explorer.blockstack.org/address/156EHDsWbvkWaHbhRXMCBRqkwQY31kfNLc |
I hereby claim:
To claim this, I am signing this object:
Keywords: software, service, patent
This is an evolution of idea #043 with the realization that availability of GPS location will soon be almost universal to anyone with a cellphone, hand held computing device or laptop. The problem remains that the answer to the question "where are you" can still be a problem to communicate. Only a small percentage of the earth's surface can be accurately identified by a street address - for the rest we must rely on ad-hoc relative location such as "near the big tree a mile past the Foo exit of the freeway Bar". Or when off-road even more ad-hoc. The alternative is to revert to the use of the canonical latitude and longitude system. Unfortunately to locate some one accurately with latitude and longitude requires up to five decimal places of accuracy (1 meter resolution), combined with one to three leading digits each of latitude and longitude and a +/- or N/S E/W indicator. That makes for a lot of information to transfer probably
| +++ dasdads | |
| '''' asdasd |
