could work, but I'm guessing
that's a pretty esoteric corner case.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sep 25, 2008, at 1:14 PM, David Fetter wrote:
On Thu, Sep 25, 2008 at 01:05:26PM -0700, Casey Allen Shobe wrote:
On Sep 15, 2008, at 7:19 PM, Tom Lane wrote:
The problem is that the people who ask for this type of feature are
usually imagining that they can put their code on
customer
a non-detrimental way thanks to proper implementation
techniques. Most people use a fraction of possible SQL techniques,
let alone most of the awesome functions that come provided in
pg_catalog. But the implementation is not bloated, so you don't see
it as a problem. :)
Cheers,
--
Casey A
l business, because then once you've
killed the competitor or lost the ability to steal more, you no longer
have the ability to keep up with customer demand, but many businesses
don't care about the long-term so much as a quick buck, unfortunately.
Cheers,
--
Casey Allen Shobe
Dat
nt, or you go out of business. This is
much the opposite of a business that provides a service.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.pos
for
example.
Companies need to fix their security architecture and keep production
isolated from development, not go down the obfuscation rathole. If
they do that and still have a threat that they think code obfuscation
would help manage, I'd love to see it.
Cheers,
--
Casey Allen
here *are* some very real and legitimate needs for this,
though it's a small minority of those who think they do.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
a
question about how and where the implementation is done than it is
about the feature itself.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
work around it by querying the catalog tables as a
non-superuser.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
autogenerated at
initdb time.
I don't find this functionality useful, but I also don't think that
it's completely worthless. There are enterprises with very different
needs and perspectives.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
don't, it's worth
doing.
I would like to clarify that I'm not saying anything like "PostgreSQL
needs / should have SAR support" in this thread, although I would
personally find them handy. I just wanted to clarify that what
"roles" means to an Oracle DBA is a
bugs, etc.
I prefer the way PostgreSQL development has been going, personally. :)
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
uced and you have to put a lot
of faith in the perl code - an exploit poses a lot of risk. If Slony
exposed it's own data to PG via custom SQL extensions, this would be
more secure by design.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via p
ield-level access controls).
It's complicated in Oracle, but there's a lot of possibilities there
that we simply cannot reproduce. But this could be extended one day. :)
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing
ield-level access controls).
It's complicated in Oracle, but there's a lot of possibilities there
that we simply cannot reproduce. But this could be extended one day. :)
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing
bugs, etc.
I prefer the way PostgreSQL development has been going, personally. :)
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
uced and you have to put a lot
of faith in the perl code - an exploit poses a lot of risk. If Slony
exposed it's own data to PG via custom SQL extensions, this would be
more secure by design.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via p
ich most of these jobs are, they are responsible for far less in
their job role, whereas the PostgreSQL DBA tends to end up responsible
for a lot more pieces of the puzzle.
Cheers,
--
Casey Allen Shobe
Database Architect, The Berkeley Electronic Press
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
r users just wanting to try out PostgreSQL on their desktop.
Of course, if your server didn't have X11 compiled (I don't see why it would),
then the graphical components would not (because they could not) be
compiled :).
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
http:/
of hardware, but cheap :).
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
http://rivyn.livejournal.com
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
wnload.
I got a private reply suggesting putting together a "distribution" of
PostgreSQL including extras, so that may be a possible route as well.
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
http://rivyn.livejournal.com
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
And this is the problem I discovered the hard way ;-).
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
http://rivyn.livejournal.com
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
L, this was replaced
by an actual value with PHP before execution)
So I guess my real question is, how can I address the same issues in
PostgreSQL?
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
http://rivyn.livejournal.com
---(end of broadcast)-
unwise time
investment, that open-source programs should focus on availability for
open-source platforms, and that people don't often run open-source databases
on Windows anyways (much more common is to see Access or Microsoft SQL). I
have stated the reasons *I* find PostgreSQL to be a bet
wish of the already very good documentation.
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
[EMAIL PROTECTED] / http://rivyn.livejournal.com
Jabber: [EMAIL PROTECTED]; ICQ: 1494523; AIM/Yahoo: SomeLinuxGuy
Free development contributor of:
> KDE toolbar icons
> Kopete
e web browser? Uh-oh...
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
[EMAIL PROTECTED] / http://rivyn.livejournal.com
Jabber: [EMAIL PROTECTED]; ICQ: 1494523; AIM/Yahoo: SomeLinuxGuy
Free development contributor of:
> KDE toolbar icons
> Kopete user interface, usability, and t
y point! But so many ignorant users fall for this and babble on
saying the exact same thing when they come attacking you for choosing
PostgreSQL.
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
[EMAIL PROTECTED] / http://rivyn.livejournal.com
Jabber: [EMAIL PROTECTED]; ICQ: 1494523;
est
speed issue with a properly designed database schema. Maybe MySQL is faster
with un-normalized tables, and that's why they like to say it's faster? I
don't know, but I really don't care if that's the case.
Vertu sæll,
--
Sigþór Björn Jarðarson (Casey Allen Shobe)
28 matches
Mail list logo
