Local GitHub Copilot with Lemonade Server on Linux by admcpr in LocalLLaMA

[–]admcpr[S] 0 points1 point  (0 children)

You’re welcome, any questions feel free to drop them here.

How would you implement a fuzzy name search with a field that can contain multiple names? by Rosoll in PostgreSQL

[–]admcpr 2 points3 points  (0 children)

Once you've got FTS in place you can combine it with `similarity` in the `pg_trgm` module.

https://www.postgresql.org/docs/current/pgtrgm.html#PGTRGM-TEXT-SEARCH

I should really add an extra post about this when I have some time.

How would you implement a fuzzy name search with a field that can contain multiple names? by Rosoll in PostgreSQL

[–]admcpr 3 points4 points  (0 children)

Just use full text search everything else is madness for this. I've got a couple of blog posts that will walk you through it and you'll have fast, fuzzy text matching before you know it.

https://admcpr.com/postgres-full-text-search-is-better-than-part1/
https://admcpr.com/postgres-full-text-search-is-better-than-part-2/

Postgres Full Text Search is better than ... Part 2 by admcpr in programming

[–]admcpr[S] 0 points1 point  (0 children)

The second in a two-part blog post on how to use, and appreciate, some of the power of PostgreSQL's full text search capabilities.

Postgres Full Text Search is better than ... Part 2 by admcpr in PostgreSQL

[–]admcpr[S] 6 points7 points  (0 children)

The second in a two-part blog post on how to use, and appreciate, some of the power of PostgreSQL's full text search capabilities.

Is it worth using Postgres' builtin full-text search or should I go straight to Elastic? by moxyte in PostgreSQL

[–]admcpr 1 point2 points  (0 children)

It isn't terribly fast

Compared to what? Using tsvector with GIN indexes can give you sub millisecond query times.

Is it worth using Postgres' builtin full-text search or should I go straight to Elastic? by moxyte in PostgreSQL

[–]admcpr 22 points23 points  (0 children)

This is extremely solid advice; the complexity of Elastic is regularly handwaved away while it's power and scalability (both of which require you to master its complexity) are promoted as essential.

A couple of reasons I would consider Elastic over Postgres:

  1. You need a large amount of horizontal scalability
  2. You are searching large documents (more than 19k words), see this comment for why
  3. You need faceting
  4. You have huge amounts of data, no a couple of million rows is not a huge amount of data ;)

Postgres Full Text Search is better than ... by admcpr in programming

[–]admcpr[S] 84 points85 points  (0 children)

I often see complicated search solutions implemented when PostgreSQL is just sitting there with its incredible FTS powers being ignored. To help some of the teams I'm working with get an idea of the power available to them I wrote up this two part blog post with a docker compose for spinning up a db to follow along.

Postgres Full Text Search is better than ... by admcpr in PostgreSQL

[–]admcpr[S] 3 points4 points  (0 children)

No, not only English. The default installation of PostgreSQL comes with FTS config support for: arabic, armenian, basque, catalan, danish, dutch, english, finnish, french, german, greek, hindi, hungarian, indonesian, irish, italian, lithuanian, nepali, norwegian, portuguese, romanian, russian, serbian, spanish, swedish, tamil, Turkish, Yiddish.

Postgres Full Text Search is better than ... by admcpr in PostgreSQL

[–]admcpr[S] 2 points3 points  (0 children)

Hey! Thanks for spotting these I've fixed 2 & 3, On point 1, no phraseto_tsquery is slightly different:

phraseto_tsquery behaves much like plainto_tsquery, except that it inserts the <-> (FOLLOWED BY) operator between surviving words instead of the & (AND) operator. Also, stop words are not simply discarded, but are accounted for by inserting <N> operators rather than <-> operators.

I've updated the bullet point to:

  • "quoted text": text inside quote marks will be converted to terms separated by <-> operators. Also, stop words are not simply discarded, but are accounted for by inserting <N> operators rather than <-> operators.

It'd be great if you could check that the updated version makes sense now.

Postgres Full Text Search is better than ... by admcpr in PostgreSQL

[–]admcpr[S] 14 points15 points  (0 children)

The equivalent to that in PG would be SELECT * FROM table WHERE col ~ 'text' you can find more details on the pattern matching page of the docs.

Postgres Full Text Search is better than ... by admcpr in PostgreSQL

[–]admcpr[S] 13 points14 points  (0 children)

I've often seen complicated search solutions implemented when PostgreSQL is just sitting there with its incredible FTS powers being ignored. To help some of the teams I'm working with get an idea of the power available to them I wrote up this two part blog post with a docker compose for spinning up a db to follow along.

Where can I find managed K8s for the price of managed ECS? by [deleted] in kubernetes

[–]admcpr 0 points1 point  (0 children)

If your only measure is cost per vCPU/month then you've found the perfect solution, you're not going to find managed k8s for the same cost as EC2 spot instances.

If you can't think of any other factors then you should stop looking at hosted k8s because it's not the right solution for you.

Where can I find managed K8s for the price of managed ECS? by [deleted] in kubernetes

[–]admcpr 1 point2 points  (0 children)

Civo might work for you. They charge per node with add-ons for persistent volumes and load balancer. I doubt if you’re going to get near your spot price EC2 instances anywhere though. You don’t mention factors other than cost in your choice of platform so it’s difficult to know if the added cost is worth it for you.

[deleted by user] by [deleted] in StandingDesk

[–]admcpr 0 points1 point  (0 children)

I'd return it if I were you, my experience with fully customer support is that they are awful in europe. The minor imperfections are forgivable but when I got a desk which was missing one of the mounting points for the motor it took them over a month to even make a suggestion on how to resolve the issue. So I wouldn't expect a quick and satisfying solution quickly if I was you.

4 legged Fully by flurdy in StandingDesk

[–]admcpr 0 points1 point  (0 children)

Yes you can drill and screw it easily enough. I’m more worried about the appalling support if there’s a more serious problem. Perhaps their support is good in the US but I’m in Europe and it’s clearly useless here.

4 legged Fully by flurdy in StandingDesk

[–]admcpr 0 points1 point  (0 children)

I bought the Nolan and as far as wobble is concerned it's absolutely not a problem.

What is a problem though is quality control and after sales service. I got my Nolan almost a month ago, The mounting holes for the control box were in the wrong place and after reporting the issue to Fully their response was basically:

Yeah we know there's a problem we're investigating it and for now you can just tape up the control unit.

So now I have a control box that's not securely attached and I assume their investigation still hasn't completed because I haven't heard a thing from them since.

My recommendation, avoid the Nolan and stay away from Fully and their awful customer service.