| From: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Storage and querying of filesystem paths |
| Date: | 2020-11-30 17:43:22 |
| Message-ID: | Ie8yE2MRHR_lq5uRzcitCNqJyo0l7j-TIOzFL6x-BpicXjRDPbR7SSD8FrRDZnfR4g4zl9FsHDM1heyTICi4luikMFBN4z8_042_j08gnYo=@protonmail.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, November 30, 2020 12:36 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Mon, 2020-11-30 at 12:05 +0000, Laura Smith wrote:
>
> > How have others approached the problem of storing and querying filesystem paths ?
> > I'm talking about *nix/*nux style paths, e.g. /home/foo/bar
> > A text column with a GIN index is an obvious possibility, but I'm interested to hear what approach others have taken ?
>
> I have not personally taken that approach, but you could give the
> ltree extension a go.
>
> Yours,
> Laurenz Albe
>
> ---------------------------------------------------------------------------------------------------------------
>
> Cybertec | https://www.cybertec-postgresql.com
Thanks Laurenz. Will take a look at ltree
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Tinker | 2020-11-30 19:28:23 | How much shared memory does Postgresql need per max_locks_per_transaction? |
| Previous Message | Nick Cleaton | 2020-11-30 15:36:23 | concurrent re-partitioning of declarative partitioned tables |