-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Sep 28, 2008 at 09:24:48PM -0700, David E. Wheeler wrote:
> On Sep 28, 2008, at 17:46, Tom Lane wrote:
>
>> BTW, I think it is (or should be) possible to create an index on
>> hstore->'mycol', so at least one of the reasons why you should *need
What you're talking about is a document based database like
StrokeDB, CouchDB. With hstore you don't need to parse content of
'aggregate' column, it provides necessary methods. Also, we tried
to speedup selects using indexes. Probably, we need to refresh our
interest to hstore, do you have any
On Sep 28, 2008, at 17:46, Tom Lane wrote:
BTW, I think it is (or should be) possible to create an index on
hstore->'mycol', so at least one of the reasons why you should *need*
to switch to a "real" database column seems bogus.
The docs say:
Indexes
hstore has index support for @> a
Andrew Dunstan wrote:
this works better but there is something fishy still - using the same
dump file I get a proper restore using pg_restore normally. If I
however use -m for a parallel one I only get parts (in this case only
243 of the 709 tables) of the database restored ...
Yes
Hello,
The datfrozenxid bug is fixed in 8.3.4,
but do I need additional operations after upgrade postgres binaries?
| Fix potential miscalculation of datfrozenxid (Alvaro)
| This error may explain some recent reports of failure
| to remove old pg_clog data.
I assume that pg_database.datfroz
> [EMAIL PROTECTED] writes:
>> Being able to insert arbitrary named values, and extracting them
>> similarly, IMHO works "better" and more naturally than some external
>> aggregate system built on a column. I know it is a little "outside the
>> box" thinking, what do you think?
>
> I'm failing to s
Simon Riggs <[EMAIL PROTECTED]> writes:
>> It does nothing AFAICS for the
>> problem that when restarting archive recovery from a restartpoint,
>> it's not clear when it is safe to start letting in backends. You need
>> to get past the highest LSN that has made it out to disk, and there is
>> no g
Not that I'm agreeing with the direction but just as a thinking experiment:
Tom Lane wrote:
[EMAIL PROTECTED] writes:
Being able to insert arbitrary named values, and extracting them
similarly, IMHO works "better" and more naturally than some external
aggregate system built on a column. I kn
On Sun, 2008-09-28 at 14:02 -0400, Tom Lane wrote:
> It does nothing AFAICS for the
> problem that when restarting archive recovery from a restartpoint,
> it's not clear when it is safe to start letting in backends. You need
> to get past the highest LSN that has made it out to disk, and there i
[EMAIL PROTECTED] writes:
> Being able to insert arbitrary named values, and extracting them
> similarly, IMHO works "better" and more naturally than some external
> aggregate system built on a column. I know it is a little "outside the
> box" thinking, what do you think?
I'm failing to see the po
Greg Stark <[EMAIL PROTECTED]> writes:
> On 27 Sep 2008, at 09:56 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> ISTM that the fundamental problem is that plpgsql doesn't distinguish
>> properly between a null row value (eg, "null::somerowtype") and a
>> row of null values (eg, "row(null,null,...)::som
> [EMAIL PROTECTED] writes:
>> Something like this:
>
>> create adhoc table foo ();
>
>> insert into foo (name, rank, serial) values ('joe', 'sargent', '42');
>
>> In an "ad-hoc" table type, when an insert is made, and a column is not
>> found, then a new varchar column is added.
>
>> I know the id
[EMAIL PROTECTED] writes:
> Something like this:
> create adhoc table foo ();
> insert into foo (name, rank, serial) values ('joe', 'sargent', '42');
> In an "ad-hoc" table type, when an insert is made, and a column is not
> found, then a new varchar column is added.
> I know the idea has a lot
I was in a discussion with someone about the difference between ad-hoc
storage systems and SQL. Yes, I know, I was rolling my eyes as well. One
thing did strike me though was the idea that a table could contain a
variable number of columns.
Something like this:
create adhoc table foo ();
insert
Markus,
* Markus Wanner ([EMAIL PROTECTED]) wrote:
> What does the subobject column for pg_shdepend buy us?
Tracking column-level ACL dependencies rather than having those
dependencies only be at the table-level. This complicates
pg_shdepend some, but simplifies the dependency handling in the
AC
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Thu, 2008-09-25 at 18:28 -0400, Tom Lane wrote:
>> After reading this for awhile, I realized that there is a rather
>> fundamental problem with it: it switches into "consistent recovery"
>> mode as soon as it's read WAL beyond ControlFile->minRecoveryPoi
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> To keep everyone who's interested up-to-date, attached is the latest
> patch. ...
> I find it a bit disturbing that a documentation patch actually removes
> more lines from the manual than adds, but it's quite understandable
> because it's no long
On Sun, 2008-09-28 at 04:03 +0300, Greg Stark wrote:
> Iirc the reason for this fuzziness came from the SQL spec definition
> of IS NULL for rows. As long as you maintain that level of spec-
> compliance I don't think there are any other important constraints on
> pg behaviour.
What does SQL
Stefan Kaltenbrunner wrote:
The sysadmin team would like to announce a planned maintenance window
for OS related updates on tribble.postgresql.org starting Sunday Sep 28
07:00 GMT (espected to last for an hour) affecting the following
publically visible services:
cvs.postgresql.org
wwwmaster.
Hi,
I have gone through the following stuff
1) previous emails on the patch
2) http://wiki.postgresql.org/wiki/In-place_upgrade
3) http://www.pgcon.org/2008/schedule/attachments/57_pg_upgrade_2008.pdf
4) http://wiki.postgresql.org/wiki/In-place_upgrade:Storage
Here is what I have understood so f
Iirc the reason for this fuzziness came from the SQL spec definition
of IS NULL for rows. As long as you maintain that level of spec-
compliance I don't think there are any other important constraints on
pg behaviour.
greg
--sorry for the top posting but the phone makes it hard to do anythi
21 matches
Mail list logo