On 4/12/19 3:11 PM, Paul van der Linden wrote:
Hi,
For my process, I needed to drop all the tables in a tablespace except one
which I truncated.
After that I would have expected to have a couple of KB max in that
folder, but there was about 200GB in it.
Did you vacuum afterwards?
There we
On 4/12/19 1:11 PM, Paul van der Linden wrote:
Hi,
For my process, I needed to drop all the tables in a tablespace except
one which I truncated.
After that I would have expected to have a couple of KB max in that
folder, but there was about 200GB in it.
There were 2 sets of files (, .1 .. .9
Hi,
For my process, I needed to drop all the tables in a tablespace except one
which I truncated.
After that I would have expected to have a couple of KB max in that folder,
but there was about 200GB in it.
There were 2 sets of files (, .1 .. .99, and the same for
id2).
Tried the various options
Got it! Thanks Andres and Tom!
Tiff
On Fri, Apr 12, 2019 at 1:07 PM Tom Lane wrote:
> Andres Freund writes:
> > On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
> >> Tiffany Thang writes:
> >>> Can someone explain the use of creating multiple indexes on the same
> >>> column?
>
> >> There is non
Andres Freund writes:
> On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
>> Tiffany Thang writes:
>>> Can someone explain the use of creating multiple indexes on the same
>>> column?
>> There is none, unless the indexes have different properties (e.g.
>> different opclasses and/or index AMs).
> We
Hi,
On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
> Tiffany Thang writes:
> > Can someone explain the use of creating multiple indexes on the same
> > column?
>
> There is none, unless the indexes have different properties (e.g.
> different opclasses and/or index AMs).
Well, it can be beneficia
On 4/11/19 1:45 AM, 김준형 wrote:
1. It spends more resources but I think this setting endure that problem.
Actually, after this setting, Windows server(include PostgreSQL server)
endures that problem more.
But I know it's not a solution.
2. No. MS-SQL SERVER, PostgreSQL Server, and Tomcat.
Wha
Tiffany Thang writes:
> Can someone explain the use of creating multiple indexes on the same
> column?
There is none, unless the indexes have different properties (e.g.
different opclasses and/or index AMs).
I'd suggest reading
https://www.postgresql.org/docs/current/indexes.html
On Fri, 12 Apr 2019 at 11:54, Tiffany Thang wrote:
> Can you provide a scenario where creating multiple indexes on the same
> column would be beneficial?
>
When you have too much disk space?
When your table writes are too fast?
Hi,
Can someone explain the use of creating multiple indexes on the same
column?
How would the optimizer determine which index to use? From my brief
testing, the optimizer picked the latest created index, testidx3. Can you
provide a scenario where creating multiple indexes on the same column would
On 04/12/2019 08:39 AM, Michael Lewis wrote:
Way to many indexes. I'm going to have a hard time convincing our
programmers to get rid of any of them )
You can create (concurrently) an identical index with a new name, then
drop old version concurrently and repeat for each. It doesn't h
11 matches
Mail list logo