Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Does anyone know why 'pg_restore -d' doesn't display the commands being
> > > executed, like you see when you don't use '-d':
> >
> > > pg_restore < /tmp/test.db
> > > pg_restore -d test < /tmp/test.db
>
Patch applied.
---
Bruce Momjian wrote:
> I found a bug in the pg_restore code. It shows up only using the tar
> format, and only on Windows XP (not Win2000 or BSD/OS). However, the
> bug exists on all platforms that don't
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Another idea if you like consistency would be:
> >
> > LOG: duration: 4.056 ms query: select * \nfrom pg_language;
>
> Speaking of consistency...
>
> Imagine someone always having log_statement on and doing some sort of
> aggregate quer
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I had a new idea on output format. Instead of converting newline to
> > "\n", and double-escaping backslashes, we add a tab after any newline,
>
> Then how would you identify the real tabs in the data?
Any log line that starts with a tab was
Bruce Momjian writes:
> I had a new idea on output format. Instead of converting newline to
> "\n", and double-escaping backslashes, we add a tab after any newline,
Then how would you identify the real tabs in the data?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end
Bruce Momjian writes:
> Another idea if you like consistency would be:
>
> LOG: duration: 4.056 ms query: select * \nfrom pg_language;
Speaking of consistency...
Imagine someone always having log_statement on and doing some sort of
aggregate query counting, say like grep '^LOG: query:' |
