Re: [HACKERS] XID wraparound and busy databases

also need to search on other indexed keys, thus we use what we call a 'broadcast query'. We'd be happy with better faster vacuums or limits on xids (or both!) -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpD0OBStu40z.pgp Description: PGP signature

Re: [HACKERS] What X86/X64 OS's do we need coverage for?

4. I just filled out the form on the buildfarm page, so I'm awaiting further instructions.... -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpVCtLZQqW0p.pgp Description: PGP signature

Re: [HACKERS] Giving up multiple postmaster + RPM issue

/local/pg7.4 and /usr/local/pg8.1, init scripts are /etc/init.d/postgres8.1, /etc/init.d/postgres7.4 That combined with some 'alternatives' magic makes things work well for the hosts at my current job. spec file(s) available on request... -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpaOCeidFNHF.pgp Description: PGP signature

[HACKERS] Latest timezone data in 8.1.4

this the correct way to do this? * Can updating the timezone data be a part of the release checklist? * Finally, is it possible to upgrade a running server with new timezone data? -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpaYwDMYHRWb.pgp Description: PGP signature

[HACKERS] MIN() performance regression 8.0 -> 8.1

--- Aggregate (cost=5524.70..5525.25 rows=1 width=8) -> Index Scan using mm_moo_summary_blog_id on mm_moo_summary (cost=0.00..5519.37 rows=2132 width=8) Index Cond: (moo_summary_b_id = 21522) (3 rows) -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpfVJMa8Upnn.pgp Description: PGP signature

Re: [HACKERS] Upcoming PG re-releases

On Sun, Dec 04, 2005 at 11:34:16AM -0500, Tom Lane wrote: > Paul Lindner <[EMAIL PROTECTED]> writes: > > To convert your pre-8.1 database to 8.1 you may have to remove and/or > > fix the offending characters. One simple way to fix the problem is to > > run your pg_du

Re: [HACKERS] Upcoming PG re-releases

dump.sql Another possible solution is to use the --inserts flag to pg_dump. When you load the resulting data dump in 8.1 this will result in the problem rows showing up in your error log. -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpmSxHGkaqYp.pgp Description: PGP signature

Re: [HACKERS] Differences in UTF8 between 8.0 and 8.1

assed through the problem character sequences. I'm still looking for an iconv that doesn't read the entire file into memory. At this point I'm looking to use the split command to process input in 1 line chunks. Sadly that can't be used i

Re: [HACKERS] Differences in UTF8 between 8.0 and 8.1

a pipe between pg_dump and psql. Anyone have any other recommendations? GNU recode might do it, but I'm a bit stymied by the syntax. A quick perl script using Text::Iconv didn't work either. I'm off to look at some other perl modules and will try to create a script so I

Re: [HACKERS] Differences in UTF8 between 8.0 and 8.1

On Sun, Oct 23, 2005 at 05:56:50AM -, Andrew - Supernews wrote: > On 2005-10-22, Paul Lindner <[EMAIL PROTECTED]> wrote: > > I've generated dumps using pg_dump from 8.0 and 8.1. Attempting to > > restore these results in > > > > Invalid UNICODE byte seq

[HACKERS] Differences in UTF8 between 8.0 and 8.1

ve.com/pgsql-patches@postgresql.org/msg08198/unicode.diff Is there any solution other than scrubbing the entire dataset to conform to the new (8.1) encoding rules? -- Paul Lindner| | | | | | | | | | [EMAIL PROTECTED] pgpkf6ogYMIyZ.pgp Description: PGP signature