Josh Berkus wrote:
> Matt,
>
> > I now agree completely. My purpose is to migrate Oracle databases to
> > Posgres, and I had thought that Oracle didn't support CURRENT_DATE,
> > CURRENT_TIMESTAMP, and so on. However, I've just learned otherwise. So,
> > I think the proper migration process for a
On Sun, 2006-11-19 at 12:03 -0800, David Fetter wrote:
> On Sun, Nov 19, 2006 at 12:01:15PM -0800, Joshua D. Drake wrote:
> > On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
> > > Tom,
> > >
> > > > Let's go with the easy fix. With regular 1GB segment size,
> > > > having a few empty files
Heikki Linnakangas wrote:
Florian G. Pflug wrote:
Joshua D. Drake wrote:
On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
Tom,
Let's go with the easy fix. With regular 1GB segment size, having a
few
empty files in the data directory isn't going to hurt anyone.
No, but it will confuse DB
Florian G. Pflug wrote:
Joshua D. Drake wrote:
On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
Tom,
Let's go with the easy fix. With regular 1GB segment size, having a few
empty files in the data directory isn't going to hurt anyone.
No, but it will confuse DBAs ("What the heck are all t
Joshua D. Drake wrote:
On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
Tom,
Let's go with the easy fix. With regular 1GB segment size, having a few
empty files in the data directory isn't going to hurt anyone.
No, but it will confuse DBAs ("What the heck are all these 0B files?"). Maybe
On Sun, Nov 19, 2006 at 12:01:15PM -0800, Joshua D. Drake wrote:
> On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
> > Tom,
> >
> > > Let's go with the easy fix. With regular 1GB segment size,
> > > having a few empty files in the data directory isn't going to
> > > hurt anyone.
> >
> > No
On Sun, 2006-11-19 at 11:28 -0800, Josh Berkus wrote:
> Tom,
>
> > Let's go with the easy fix. With regular 1GB segment size, having a few
> > empty files in the data directory isn't going to hurt anyone.
>
> No, but it will confuse DBAs ("What the heck are all these 0B files?").
> Maybe
> we
Tom,
> Let's go with the easy fix. With regular 1GB segment size, having a few
> empty files in the data directory isn't going to hurt anyone.
No, but it will confuse DBAs ("What the heck are all these 0B files?"). Maybe
we should add code to VACUUM to look for these empty file segments and un
Tom Lane wrote:
I think that the easiest fix might be to not remove no-longer-used
segment files during a truncate, but simply reduce them to zero size
rather than delete them. Then any open file pointers aren't
invalidated. The only alternative I can see is to invent some new
signaling mechani
Tom Lane wrote:
>
> I think that the easiest fix might be to not remove no-longer-used
> segment files during a truncate, but simply reduce them to zero size
> rather than delete them. Then any open file pointers aren't
> invalidated. The only alternative I can see is to invent some new
> signal
Hi,
Am 15.11.2006 um 15:34 schrieb Gurjeet Singh:
=
.) The SELECTs in the pg_advise are returning wrong results, when
the same index is suggested twice, because of the SUM() aggregates.
I don't think that this is a bug. If the same index is recommended
for two different queries it will ap
11 matches
Mail list logo
