red_buffers gets my vote, on my test table with
> 50,000,000 rows it takes about 8 minutes to create an index using the
> default effective_cache_size. With effective_cache_size set to 6GB
> (machine has 8GB) its still going an hour later.
Agreed. I think using shared_buffers as a
interesting*. I'll post stats tomorrow
when I'm in the office.
--
Jonah H. Harris, Senior DBA
myYearbook.com
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
btain a feature that
> so far as I've heard there is precisely zero demand for.
We have a customer that wants to use it as part of a MySQL-to-Postgres
migration.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornal
On Jan 28, 2008 8:21 AM, Gokulakannan Somasundaram <[EMAIL PROTECTED]> wrote:
> I am not seeing my mail getting listed in the archives. So i am just
> resending it, in case the above one has got missed.
It was sent. Archive processing is delayed.
--
Jonah H. Harris, Sr. Softwa
s a
> pretty trivial patch, but seeing how late we are in the 8.3 release
> cycle, I thought I'd better post it for comment anyway.
+1
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Stre
I will take care, that i won't repeat the stated
> mistakes again.
>
> The Missing of Thick Keyword - i don't know how it got removed.
>
>
>
> Thanks,
> Gokul
>
>
>
> On Jan 23, 2008 10:49 PM, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
> >
I have them
fixed and will submit the patch back here if you'd like. Or, you can
fix it. It's up to you :)
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTE
On Jan 15, 2008 5:04 AM, Neil Conway <[EMAIL PROTECTED]> wrote:
> > Any thoughts whether to apply or not?
>
> Seems like a much more sane approach to me -- +1.
Agreed, sounds and looks better to me. +1
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
Enterp
On Nov 28, 2007 3:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Entirely removing the example of how to do it with rules doesn't
> seem like a good idea.
Agreed.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax:
me not without
exposing any implementation details outside the type.
Seems like too much work for a fairly simple use-case.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
asis.
I'm also wondering what's the point of comparing attbyval etc when
you've already checked it's the same type OID.
True.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor|
VARCHAR(32) NOT NULL,
PRIMARY KEY (test_id));
ALTER TABLE test_tbl ALTER COLUMN test_name TYPE VARCHAR(64);
I can't find any case where this doesn't work... but perhaps you guys
know of some.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporat
On 9/1/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Attached is a draft patch that makes rules support RETURNING ...
What format is that patch in? Either something's wrong or Gmail just
went really wacko.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB
- Possibly For
Tom Lane - Against
Jonah Harris - For
David Fetter - For
Josh Drake - Against
Andrew Dunstan - Against
Josh Berkus - For
Dave Page - For
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor
One of the points, taken a little out of context, was made by Tom.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb
On 8/26/06, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
So, yes, it is used, and by far more that just hard core hackers.
OK. Kewl. I just hadn't run into many people (except hackers) that
knew about it. Thanks for sharing that.
--
Jonah H. Harris, Software Architect | phone: 7
c but would gladly appreciate public or private
proof regarding pgfoundry's popularity.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08
hink it's going to get enough attention
and enough of a user following to make it worth the time of one of the
core developers to pick it up.
Of course, I may always be wrong. Perhaps pgfoundry is more popular
than I've seen in past experience. Maybe one of the core developers
d
On 8/25/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Sorry, we did not get enough feedback to include this in 8.2. Please
add it to pgfoundry and let's see how it goes.
Yep... it's too bad. A new feature no other database has now goes to
it's final resting place on p
On 8/5/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> Here's the updated patch with DELETE RETURNING removed. This isn't
> really an issue because no one wanted DELETE RETURNING to begin with.
I don't have th
On 8/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
UPDATE tries to place the new tuple on the same page it's already
on.
I think he meant for INSERT.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S
RNS instead
I don't have a strong feeling either way, but now is the time to
decide.
I don't care either way, RETURNS is fine I guess.
OK, but we need a final version soon.
Sure thing.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation
tions requested.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
pg82-iuret-073106.patch
Descripti
ties to the implementation, I need something
that quickly returns boolean or fails entirely when it detects same.
From an application development standpoint, it would be nice to have a
strictly numeric version returning function for checking server
compatibility.
--
Jonah H. Harris, Software Archit
On 6/6/06, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
On 6/6/06, ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> This is a patch for table/index fillfactor control discussed in
> http://archives.postgresql.org/pgsql-hackers/2006-06/msg00175.php
There's 4 shift/reduce co
plan to fix this?
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
---(end o
really needs two levels of targetlist, as does UNION.
Maybe if we thought a little bit larger we could clean up all of that
messiness at one stroke.
Have you had any ideas on how to best accomplish this?
--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324
--
On 4/3/06, Mark Wong <[EMAIL PROTECTED]> wrote:
> Once I get a test system going again in the lab I'll start
> posting some data. I'm planning a combination of
> block sizes (BLCKSZ and XLOG_BLCKSZ) and number
> of WAL buffers.
Cool. I'm looking forward to
On 3/14/06, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
Maybe one of the proponents could put together a comparison matrix ofhow this is done in each of the databases previously mentioned.
Hans,
I don't have time to do this, would you like to take a stab at it?
-- Jonah H. Harri
On 3/13/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Does any SQL-like database system other than Oracle have this feature?
I know that SQL Server, DB2, SAP DB/MAX DB, and Mimer have it.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
oing to start a new thread to propose this clearly.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
any sub-discussions to be useful. For functionality descriptions, see the Oracle docs. I'm not averse to straying from Oracle's way of doing it if it makes sense.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
a
small cost only when using synonyms as well.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
GRR, not enough coffee yet today :(
Jonah now enjoys some SumatraOn 3/8/06, Jonah H. Harris <[EMAIL PROTECTED]
> wrote:I agree wholeheartedly.
regarding "we should take a fresh look at the problem rather than just blindly copying a construct from Oracle".
SELECT dblink('
ither. I'm glad we have the contrib module, but there's a lot of
nicer things we could do there as well. Not because it's an
Oracle thing, but because it's great functionality to have.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
most
cases), or to set the search path to $user,public,hr. Again, this
doesn't cover the "same-named tables in multiple schemas" argument, but
it does illustrate that PostgreSQL's namespace scoping remains the same.
The question is whether we want to offer the functionality
the same breath we way things like "we're not going to copy
Oracle/SQL Server/Sybase/DB2 features." You're right, we all
agree that we shouldn't just add something because [insert database
vendor name here] has it, but we should at least have an open mind and
look at it from
st in other schemas or where there are duplicate object names
across schemas.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
ve that limitation so we don't need that usage either.
No, one could do fully qualified naming in Oracle; synonyms do have other purposes outside of this single one listed.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
h is surely reduced but it is in no way wholly eliminated
either. Some users don't have the ability to choose how
vendors/developers write their software and they can't easily just
convert an entire application to use search_path where they once had
synonyms (especially if the application is f
7;t really make sense), the cost would be the same whether
they're used or not during searching.-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
On 3/7/06, Hans-Jürgen Schönig <[EMAIL PROTECTED]> wrote:
we should definitely work together.what is the status of your patch?maybe we can discuss this off list?
The last time I worked on it was on 8.0 (I think), but it wouldn't take
much to get it up to speed on 8.2. It's actually very similar to
out
extending pg_class and pg_proc. Even so, this would still add
overhead to catalog searches.
Just for the record, this is lacking pg_dump support as well asdocumentation.
True.
I'd be glad to submit my patch and/or cleanup this one if its something the community would be willing to accept.-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
On 3/2/06, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
On 3/2/06, Tom Lane <[EMAIL PROTECTED]
> wrote:
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:> INSERT/UPDATE/DELETE seem to work fine in normal operation but there is an
> error with DELETE RETURNING when use
On 3/2/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:> INSERT/UPDATE/DELETE seem to work fine in normal operation but there is an> error with DELETE RETURNING when used through PL/pgSQL.
Probably other places too. I don&
o looking into it. Any suggestions are always welcome. -- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation
732.331.1324
NING
DELETE FROM test_tbl WHERE test_id = current_rec.test_id
RETURNING * INTO current_rec;
-- This DOES NOT WORK
RAISE NOTICE 'test_id is %', current_rec.test_id;
RAISE NOTICE 'test_name is %', current_rec.test_name;
RETURN;
END;
$$ LANGUAGE plpgsql;-- J
47 matches
Mail list logo
