[GENERAL] RAM is good!

2008-12-07 Thread Scott Ribe
I know that my database is not that big (4-5GB), but I am shocked at how well it's performing during a RAID rebuild. For light use, the difference is hardly noticeable. Nothing like avoiding hitting the disk ;-) -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 722-0567 voice -

Re: [GENERAL] RAM is good!

2008-12-07 Thread Scott Marlowe
On Sun, Dec 7, 2008 at 10:00 AM, Scott Ribe <[EMAIL PROTECTED]> wrote: > I know that my database is not that big (4-5GB), but I am shocked at how > well it's performing during a RAID rebuild. For light use, the difference is > hardly noticeable. Nothing like avoiding hitting the disk ;-) Our db si

[GENERAL] ERROR: compressed data is corrupt

2008-12-07 Thread Scott Ribe
I'm seeing that now when trying to run an update. Is there anything I should investigate? This is a test database, and I can just wipe it and restore from dump. BTW, this is not related to my earlier message about rebuilding a RAID ;-) -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/

[GENERAL] ERROR: compressed data is corrupt, ignore earlier message

2008-12-07 Thread Scott Ribe
Oops. I switched over to a test machine (laptop) that hadn't been used in a while. Didn't think to check pg version before loading up test db. I'm running 8.3.1. S... Never mind. -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 722-0567 voice -- Sent via pgsql-general mai

[GENERAL] domain+enum

2008-12-07 Thread Grzegorz Jaśkiewicz
One thing I don't understand, can someone please explain that to me: (that's on 8.4, but it "works" same way on 8.3) CREATE TYPE rcount AS ENUM ( 'one', 'two', 'three' ); CREATE DOMAIN foocount AS rcount DEFAULT 'one' NOT NULL; CREATE DOMAIN foostamp AS bigint NOT NULL DEFAULT (EXTRACT(epo

[GENERAL] shared disk failover

2008-12-07 Thread Jaime Casanova
Hi, any one has doing this... is there a good tutorial o directions for it? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make

Re: [GENERAL] tuples

2008-12-07 Thread Harvey, Allan AC
> I have a question concerning psql. I found that psql has a defined > command '-t' and that it turns off printing of column names > and result > row count footers, etc. > > what I look for, is a command, which would turn off result row count > footer, but would print column names. > > is the

Re: [GENERAL] ALTER TABLE .....Error: Must be owner of the table

2008-12-07 Thread Tom Lane
"Josh Harrison" <[EMAIL PROTECTED]> writes: > How can I give the ALTER permission You can't grant ALTER permission --- that's only allowed to the table owner. However, you could make thw table be owned by a group role and grant membership in that role. regards, tom lane

Re: [GENERAL] COPY error with null date

2008-12-07 Thread Bill Todd
Joshua D. Drake wrote: On Fri, 2008-12-05 at 12:00 -0700, Bill Todd wrote: Joshua D. Drake wrote: On Thu, 2008-12-04 at 19:35 -0700, Bill Todd wrote: null as IS NULL results in the following error. ERROR: syntax error at or near "is" LINE 5: null as is null

Re: [GENERAL] COPY error with null date

2008-12-07 Thread Tom Lane
Bill Todd <[EMAIL PROTECTED]> writes: > I am beginning to suspect this is impossible. That's correct: see the COPY reference page. A quoted value is never considered to match the NULL string. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgr

Re: [GENERAL] Planner picking topsey turvey plan?

2008-12-07 Thread Tom Lane
Glyn Astill <[EMAIL PROTECTED]> writes: > Does anyone know how I can change what I'm doing to get pgsql to pick a > better plan? You've provided no evidence that this is a bad plan. In particular, the plan you seem to think would be better would involve an estimated 153 iterations of the cost-15

Re: [GENERAL] Unique constaint violated without being violated

2008-12-07 Thread Dot Yet
funny!! :) too bad, i also noticed it only after reading Merlin's response :) On Sat, Dec 6, 2008 at 11:12 AM, Sebastian Tennant <[EMAIL PROTECTED]>wrote: > Quoth "Merlin Moncure" <[EMAIL PROTECTED]>: > > It looks to me like you are setting the whole table to the same > > address in the update st

Re: [GENERAL] Monty on MySQL 5.1: "Oops, we did it again"

2008-12-07 Thread Gurjeet Singh
As I read it, he is supportive of the community process that PG follows; I am not so sure he promotes Postgres though :) On Thu, Dec 4, 2008 at 3:56 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote: > Jason Long wrote: > > Greg Smith wrote: > > > I wonder if I'm the only one who just saved a copy of t

Re: [GENERAL] Prepared statement already exists

2008-12-07 Thread Tomasz Ostrowski
On 2008-11-20 12:56, WireSpot wrote: On Thu, Nov 20, 2008 at 10:56, Albe Laurenz <[EMAIL PROTECTED]> wrote: Do you still need the old prepared statement? If not, you can simple DEALLOCATE it and then try the PREPARE again. Yes, I'd like to keep the old statements, that's part of the perks --

Re: [GENERAL] Prepared statement already exists

2008-12-07 Thread WireSpot
On Mon, Dec 8, 2008 at 09:17, Tomasz Ostrowski <[EMAIL PROTECTED]> wrote: > So: > > sql_md5 = md5(sql); > try { >PREPARE sql_md5 AS sql; > } catch (SQLException e) { >if (! e.getSQLState().equals("42P05")) { >throw e; >} > } > EXECUTE sql_md5; Yeah, well, li