On 2009-04-03, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2009-04-03 at 18:03 +0100, Greg Stark wrote:
I wonder if we need a whole class of index algorithms to deal
specifically with read-only tables
I think we can drop the word index from the sentence as well.
Read-only isn't an
G'day hackers,
I had some hand-wavy thoughts about some potential gains for
postgres in the data archiving/warehousing area. I'm not able
to do any work myself on this, and don't actually have a
pressing need for it so I'm not requesting someone do it, but
I thought it might be worth discussing
G'day Gavin,
In maillist.postgres.dev, you wrote:
On Thu, 1 Feb 2007, Chris Dunlop wrote:
The main idea is that, there might be space utilisation and
performance advantages if postgres had hard read-only
tables, i.e. tables which were guaranteed (by postgres) to
never have their data
G'day,
There seems to be a kind of statement parsing problem in 7.4.5
(from debian postgresql-7.4.5-3, i386).
Either that, or I'm missing something...
The following script:
--
create table t1 ( foo1 integer, foo2 integer );
Replying to my own post, thanks to the assistance of Paul
Bort...
On Wed, Sep 15, 2004 at 11:43:47PM +1000, Chris Dunlop wrote:
There seems to be a kind of statement parsing problem in 7.4.5
(from debian postgresql-7.4.5-3, i386).
Either that, or I'm missing something...
\echo
Hi,
There seems to be a minor bug related to permissions. If you create a
table and grant permissions on that table to someone else, you lose your
own permissions (note: do this as a non-dbadmin account):
testdb= create table tester ( test int4 );
CREATE
testdb= insert into tester
