Greg Stark <[EMAIL PROTECTED]> writes:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
>> Ãhel kenal päeval, L, 2006-06-03 kell 10:43, kirjutas Jim Nasby:
>>> Might also be worth adding analyze delay settings, ala
>>> vacuum_cost_delay.
ANALYZE already respects the vacuum delay settings.
>> Actua
Greg Stark wrote:
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
One thought I had was to force Windows to use CVS export rather than update.
This has 2 disadvantages: it requires a complete repo fetch every run, even
if we don't need to do anything because nothing has changed, and it also
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> One thought I had was to force Windows to use CVS export rather than update.
> This has 2 disadvantages: it requires a complete repo fetch every run, even
> if we don't need to do anything because nothing has changed, and it also
> means we can't repo
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
> >
> > For use case, consider this:
> >
> > COPY mytable TO '| rsh [EMAIL PROTECTED] > test ';
> >
> > so you can COPY to another server directly.
> >
> Why not rsh psql -c "\copy foobar to test" ?
Who knows? The sysadmin could
Hannu Krosing <[EMAIL PROTECTED]> writes:
> Ãhel kenal päeval, L, 2006-06-03 kell 10:43, kirjutas Jim Nasby:
>
> > Might also be worth adding analyze delay settings, ala
> > vacuum_cost_delay.
>
> Actually we should have delay settings for all potential
> (almost-)full-scan service ops, - V
> Unfortunately, this fell over first time out:
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=loris&dt=200
6-06-04%2012:09:33
> The fix handled directories, but we got a false positive from
> a rename not being immediate either, it seems. Bloody Windows!
Are you running this from msys or fr
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
>>> Another option would be to re-run cvs up one more time if we get any
>>> unexpected files. It sounds like that would fix this issue on windows
>>> machines, while still ensuring we had a clean repo to work from.
> So what I'm going to try instead is
I said:
>>
>> Another option would be to re-run cvs up one more time if we get any
>> unexpected files. It sounds like that would fix this issue on windows
>> machines, while still ensuring we had a clean repo to work from.
>>
>
> please see the new release of the buildfarm client, in which I have
Bruce Momjian wrote:
For use case, consider this:
COPY mytable TO '| rsh [EMAIL PROTECTED] > test ';
so you can COPY to another server directly.
Why not rsh psql -c "\copy foobar to test" ?
Regards,
Andreas
---(end of broadcast)---
Greg Stark <[EMAIL PROTECTED]> writes:
> I see improvements up to around 256M blocks or so, but my data is pretty
> questionable since I'm busy watching tv in Mythtv in another window. It's on
> another drive but it still seems to be making the numbers jump around a bit.
Oops, I meant blocks of 2
10 matches
Mail list logo
