On Fri, 2024-10-11 at 00:19 +0530, sud wrote:
> I have never used any 'hash index' but saw documents in the past suggesting
> issues
> around hash index , like WAL doesnt generate for "hash index" which means we
> can't
> get the hash index back after crash also they are not applied to replicas e
They are extremely efficient for joins!!!
Yahoo Mail: Search, Organize, Conquer
On Thu, Oct 10, 2024 at 2:52 PM, Christophe Pettus wrote:
> On Oct 10, 2024, at 11:49, sud wrote:
>
> Hi,
> I have never used any 'hash index' but saw documents in the past suggesting
> issues around hash
On 2024-10-10 21:44 +0200, sud wrote:
> Not yet confirmed, but actually somehow we see the DB crashed repetitively
> a few times and teammates suspecting the cause while it tried extending
> this hash index.
Your first mail says that you're using version 15.4. You should
consider upgrading to 15.
On Fri, Oct 11, 2024 at 12:51 AM Erik Wienhold wrote:
> On 2024-10-10 20:49 +0200, sud wrote:
> > However, we are seeing that one of the databases has multiple hash
> indexes
> > created. So I wanted to understand from experts here, if it's advisable
> in
> > any specific scenarios over B-tre des
On 2024-10-10 20:49 +0200, sud wrote:
> However, we are seeing that one of the databases has multiple hash indexes
> created. So I wanted to understand from experts here, if it's advisable in
> any specific scenarios over B-tre despite such downsides?
Two things come to my mind:
1. Btree puts a l
> On Oct 10, 2024, at 11:49, sud wrote:
>
> Hi,
> I have never used any 'hash index' but saw documents in the past suggesting
> issues around hash index , like WAL doesnt generate for "hash index" which
> means we can't get the hash index back after crash also they are not applied
> to repl
Hi,
I have never used any 'hash index' but saw documents in the past suggesting
issues around hash index , like WAL doesnt generate for "hash index" which
means we can't get the hash index back after crash also they are not
applied to replicas etc. And also these indexes can not be used for range
q
I wrote:
> On second thought, just guarding the pg_tablespace_size() call and
> reporting an unknown size when permissions are insufficient is better,
> so that \db+ still lists all tablespaces like \db does.
And here's a patch that does that. It also adds a few words to the docs
to mention that
On 10/10/24 02:54, Thürmann, Andreas wrote:
Please excuse the late reply. I didn't have time to continue working on
this project.
I still don't get a response to the query. The query continues
indefinitely and the data output window shows only „Waiting for the
query to complete...“
In the S
On Thu, Oct 10, 2024 at 4:19 PM Erik Wienhold wrote:
> > > On 2024-10-10 14:35 +0200, Dominique Devienne wrote:
> > > > On a related but different matter, is it normal not having access to a
> > > > single tablespace makes the whole output disappear?
> On second thought, just guarding the pg_table
I wrote:
> > On 2024-10-10 14:35 +0200, Dominique Devienne wrote:
> > > On a related but different matter, is it normal not having access to a
> > > single tablespace makes the whole output disappear?
> > >
> > > ddevienne=> \db+
> > > ERROR: permission denied for tablespace hdd_data
> >
> > This
I wrote:
> On 2024-10-10 14:35 +0200, Dominique Devienne wrote:
> > On a related but different matter, is it normal not having access to a
> > single tablespace makes the whole output disappear?
> >
> > ddevienne=> \db+
> > ERROR: permission denied for tablespace hdd_data
>
> This lacks permissio
On Thu, Oct 10, 2024 at 3:40 PM Erik Wienhold wrote:
> On 2024-10-10 14:35 +0200, Dominique Devienne wrote:
> > Hi. Why isn't the ::regrole::text cast working as usual?
> > Aren't the OIDs for grantor and grantee returned by acldefault() valid
> > ROLEs?
>
> You must call acldefault() with spcown
On 2024-10-10 14:35 +0200, Dominique Devienne wrote:
> Hi. Why isn't the ::regrole::text cast working as usual?
> Aren't the OIDs for grantor and grantee returned by acldefault() valid ROLEs?
>
> C:\Users\ddevienne>psql service=...
> psql (17.0)
> SSL connection (protocol: TLSv1.3, cipher: TLS_AES
Hi. Why isn't the ::regrole::text cast working as usual?
Aren't the OIDs for grantor and grantee returned by acldefault() valid ROLEs?
C:\Users\ddevienne>psql service=...
psql (17.0)
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384,
compression: off, ALPN: postgresql)
Type "help"
15 matches
Mail list logo