Tom Lane wrote:
Rikardo Tinauer <[EMAIL PROTECTED]> writes:
I am wondering if you are considenring supporting MDX syntax in PostgreSQL?
Is there a standard for that, or is it just something
Microsoft-proprietary? Stuff that is in the SQL2003
standard is generally on our "wish list" at some l
On Sat, Dec 31, 2005 at 10:34:51AM -0500, Matthew T. O'Connor wrote:
> Anyone think it might be reasonable to add a GUC option that tells
> autovacuum to monitor for wraparound only, and not for more general
> usage based vacuuming? Something like autovac_wraparound_only. Not
> sure I like the
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> Anyone think it might be reasonable to add a GUC option that tells
>> autovacuum to monitor for wraparound only, and not for more general
>> usage based vacuuming? Something like autovac_wraparound_only. Not
>> sure I like the idea, but thought
Rikardo Tinauer <[EMAIL PROTECTED]> writes:
> I am wondering if you are considenring supporting MDX syntax in PostgreSQL?
Is there a standard for that, or is it just something
Microsoft-proprietary? Stuff that is in the SQL2003
standard is generally on our "wish list" at some level
(no guarantees
=?UTF-8?B?SnVyZSBMb8W+YXI=?= <[EMAIL PROTECTED]> writes:
> I have a big problem. I dropped wrong table. I do have very recent dump,
> but I would need to read wal (write ahead log) files somehow, to see
> last 60 entries that were made. Then I can enter them manually.
> Is there any way to make w
Anyone think it might be reasonable to add a GUC option that tells
autovacuum to monitor for wraparound only, and not for more general
usage based vacuuming? Something like autovac_wraparound_only. Not
sure I like the idea, but thought it might be worth some discussion.
I believe 8.1 will
Thanks Chris: I will contact you if they decided to go with this.
Pamela
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Travers
Sent: Wednesday, December 28, 2005 10:12 AM
To: [EMAIL PROTECTED]
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERA
Tom ~
Right you are! I added some code to trim off the schema name, and it works
fine.
You also alerted me to the NOTICE facility. (I'm new to PostgreSQL, and
have been learning it in "wade right in" mode rather than properly studying
the whole environment.) I have a "PostgreSQL for Dummies" q
On Sat, Dec 31, 2005 at 05:18:19PM +0100, Karsten Hilbert wrote:
> We will (in GNUmed) eventually have to implement row level
> security. The current thinking is by restricting access to
> the tables and setting up views that always do "... where
> user=current_user" to limit the viewable data set
Sorry, found them. They were the first hit on a Google
search I fired off while writing the last post.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
---(end of broadcast)---
TIP 4: Have you sear
On Thu, Dec 29, 2005 at 09:22:09AM -0800, Marc Munro wrote:
> http://pgfoundry.org/projects/veil/
Marc, is there a higher level written summary available
somewhere to be read to understand conceptually how you
implemented row level security ?
We will (in GNUmed) eventually have to implement row l
Jaime Casanova wrote:
But if VACUUM fixes the wraparound issue, shouldn't even a badly
configured autovacuum make the wraparound not be a problem in 8.1? Or did
I miss understand how this works?
but you can disable autovacuum (i do not why you can do something like
that but i guess someone
- Original Message -
From: "Harry Jackson" <[EMAIL PROTECTED]>
To:
Sent: Saturday, December 31, 2005 12:39 AM
Subject: Re: [GENERAL] Forum Software
On 12/30/05, Scott Marlowe <[EMAIL PROTECTED]> wrote:
Also, as a big proponent of PHP, I have to admit that it's quite easy
to
write
13 matches
Mail list logo
