Christopher Browne wrote:
The world rejoiced as [EMAIL PROTECTED] (Gaetano Mendola) wrote:
I think is a good Idea put a fflush after:
fprintf(LOGOUTPUT, "[%s] %s\n", timebuffer, logentry);
I thought I had put fflush()es at all the interesting locations...
I just looked through the code
The world rejoiced as [EMAIL PROTECTED] (Gaetano Mendola) wrote:
> I think is a good Idea put a fflush after:
>
> fprintf(LOGOUTPUT, "[%s] %s\n", timebuffer, logentry);
I thought I had put fflush()es at all the interesting locations...
Apparently it was an error to not go to the effort of making
Gaetano Mendola wrote:
Vivek Khera wrote:
"MTO" == Matthew T O'Connor <[EMAIL PROTECTED]> writes:
Then it just sits there. I started it at 11:35am, and it is now
3:30pm.
MTO> Weird Alphabetically speaking, is vkmlm."public"."user_list"
be the
MTO> last table in the last schema in the la
This has been fixed and will be in 7.4.1.
---
Vivek Khera wrote:
> > "LR" == Larry Rosenman <[EMAIL PROTECTED]> writes:
>
> >> I'd be curious to see the output of this program on other platforms
> >> and other compilers
On Fri, 2003-12-05 at 16:38, Neil Conway wrote:
>
> (1) Can you confirm that the VACUUM FULL on site B actually
> removed all the tuples you intended it to remove? Concurrent
> transactions can limit the amount of data that VACUUM FULL is
> able to reclaim. If you run
Steve Wampler <[EMAIL PROTECTED]> writes:
> Hmmm, I have a feeling that's not as obvious as I thought... I can't
> identify the index (named 'id_index') in the output of vacuum verbose.
In 7.2, the index reports look like
Index %s: Pages %u; Tuples %.0f.
and should appear in the part of t
On Fri, Dec 05, 2003 at 09:54:52PM -0500, Robert Treat wrote:
>...
> A vacuum verbose could give you a good indication if you need to reindex,
> compare the # of pages in the index with the # in the table.
Hmmm, I have a feeling that's not as obvious as I thought... I can't
identify the index (
On Fri, Dec 05, 2003 at 09:54:52PM -0500, Robert Treat wrote:
> On Friday 05 December 2003 16:51, Steve Wampler wrote:
> > I need some help tracking down a sudden, massive slowdown
> > in inserts in one of our databases.
> >
> > PG: 7.2.3 (RedHat 8.0)
> >
> > Background. We currently run nearly i
