[EMAIL PROTECTED] wrote:
Hello,
I want to ask if there is something like nomount state or close database state
in which I can acces postgresql to drop database or to do some other stuff.
Because when there are some connections, drop database is not
possible. Or is this done some other way?
Ivan Sergio Borgonovo wrote:
Yeah... but how can I effectively enforce the policy that ALL input
will be passed through prepared statements?
Code reviews are about the only way to enforce this.
If I can't, and I doubt there is a system that will let me enforce
that policy at a reasonable
Gregory Stark wrote:
paul rivers [EMAIL PROTECTED] writes:
If I can't, and I doubt there is a system that will let me enforce
that policy at a reasonable cost, why not providing a safety net that
will at least raise the bar for the attacker at a very cheap cost?
How do you do
chuckee wrote:
paul rivers-2 wrote:
chuckee wrote:
1) how do I find out the size, in MB, of a particular table (called
'capture' in this case).
I tried entering the SQL query SELECT (pg_tablespace_size('capture'));
The result was the following:
ERROR: tablespace capture does not exist
chuckee wrote:
1) how do I find out the size, in MB, of a particular table (called
'capture' in this case).
I tried entering the SQL query SELECT (pg_tablespace_size('capture'));
The result was the following:
ERROR: tablespace capture does not exist
You're looking for
Micah Yoder wrote:
Just curious, would PostgreSQL be considered secure for applications involving
financial matters where the clients have a direct database logon?
First, to clarify, I'm not in a serious position to write such an application.
I'm just wondering. :-) If it is possible, I
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 14 Mar 2008 02:00:39 -0600
Micah Yoder [EMAIL PROTECTED] wrote:
Maybe it's nuts to consider such a setup (and if you're talking a
major bank it probably is) ... and maybe not. At this point it's
kind of a mental
Tom Lane wrote:
In connection with my Red Hat duties I've had to look at it occasionally
:-(. They definitely have a lower standard for commenting than we do.
I sure hope that there is unpublished documentation somewhere ...
And cut into the very lucrative figuring out the MySQL source code
Reece Hart wrote:
On Tue, 2008-03-11 at 06:47 -0700, rrahul wrote:
Any major clients of the two.
You can add you own points too.
Perhaps someone can comment on current MySQL backups procedures. I
believe that MySQL used to (still does?) require shutdown to be backed
up. I don't know
David Potts wrote:
This is not a flame about current or previous release of Postgres.
I have just gone through the awful experience of upgrading from Postgres
8.2 to 8.3 with a database that had one of the many Postgres extensions
included. The problem comes down to the way that Postgres
Alvaro Herrera wrote:
Ivan Sergio Borgonovo wrote:
On Wed, 12 Mar 2008 09:13:14 -0700
paul rivers [EMAIL PROTECTED] wrote:
For a database of InnoDB tables, people tend to replicate the
database, and then backup the slave (unless the db is trivially
That recalled me
Scott Marlowe wrote:
On Wed, Mar 12, 2008 at 1:02 PM, paul rivers [EMAIL PROTECTED] wrote:
- Auto_increment columns as pkeys in InnoDB tables are practically
required, yet severely limited scalability due to how a transaction
would lock the structure to get the next auto-increment
Jorge Godoy wrote:
Em Monday 03 March 2008 08:08:36 Raymond O'Donnell escreveu:
On 03/03/2008 11:01, dfx wrote:
The question il: Is there a method to avoid to insert the addesses of
the clients in the pg_hba.conf and to allow connections from internet
with security assured only by
Collin wrote:
But make it hostssl instead of host, to require some
cryptography in the channel used, specially to authenticate the
connection.
Opening your access to everyone without crypto sounds like something
you don't want to do. Specially if users can change their own
passwords...
Gordon wrote:
On Feb 26, 5:26 pm, [EMAIL PROTECTED] (Gregory Stark) wrote:
Norman Peelman [EMAIL PROTECTED] writes:
My options are, as far as I can tell,
1) replace the Database PDO extending class with something else that
provides query results caching in PHP, or
2) get
Lew wrote:
Tom Lane wrote:
There never was a 7.1.4 release, so I suspect the OP meant 7.4.1
not that that speaks very much better for his software maintenance
habits. Even with the more charitable interpretation, it's a version
that was obsoleted four years ago next week.
In my
Phoenix Kiula wrote:
I'm glad I didn't go from 8.2.3 to 8.3 straight!
http://ogasawalrus.com/blog/node/462
Going from 8.2.4 and 8.2.6 to 8.3.0 has been painless for me. However,
unlike the blogger you cite, I read the directions before, not after,
attempting it.
Paul
Tony Caduto wrote:
paul rivers wrote:
Going from 8.2.4 and 8.2.6 to 8.3.0 has been painless for me.
However, unlike the blogger you cite, I read the directions before,
not after, attempting it.
The blogger has a point about pg_dump and restore, it could be much
better, for example
Stephen Cook wrote:
Magnus Hagander wrote:
I would guess they're referring to the ability to pin a table into
memory, so that it always stays in the cache regardless of what else
the database is doing. There is a narrow use-case where this can be
very useful, but it can also be a very
Willy-Bas Loos wrote:
Hi,
How, using psql, can i connect to a PostgreSQL server that has
sslhost in the pg_hba.conf file?
I can't find the SSL option in the manpage.
thx,
WBL
Make sure both your server and client have ssl support compiled in. I'm
not sure if that's there by default with
Alex Vinogradovs wrote:
Yes, I enter query manually while testing. Here are explain plans :
for select count(*) from poll_3 where eid = 72333
Aggregate (cost=34697.64..34697.65 rows=1 width=0)
- Seq Scan on poll_3 (cost=0.00..34650.40 rows=18893 width=0)
Filter: (eid = 72333)
paul rivers wrote:
Alex Vinogradovs wrote:
Yes, I enter query manually while testing. Here are explain plans :
for select count(*) from poll_3 where eid = 72333
Aggregate (cost=34697.64..34697.65 rows=1 width=0)
- Seq Scan on poll_3 (cost=0.00..34650.40 rows=18893 width=0)
Filter
Alex Vinogradovs wrote:
Hello all,
I have a table which is partitioned by range into 10 pieces with
constraint exceptions. Constraint exceptions is enabled in server
configuration too. For some reason, queries to the master table
are still slower than direct queries against partitions. Is
Is there an existing way to enforce password complexity for password
authentication?
I am not seeing anything in the docs, and I can only turn up this
reference to a pending patch for 8.2 (bottom of page):
http://www.postgresql.org/community/weeklynews/pwn20061210
Thanks in advance for
Tom Lane wrote:
Kevin Hunter [EMAIL PROTECTED] writes:
However, I'm not a DBA and only minimally know what's involved in doing
the job, so I don't have ammo to defend (or agree?) with my friend
when he says that Postgres requires a DBA and MySQL doesn't so that's
why they choose the latter.
Sean Z. wrote:
Hi,
I partitioned a table events into 31 tables, based on day of
event_time.
I did 3 steps to setup partition, after creating partition tables:
1. Add the constraint to the 31 partition tables like:
ALTER TABLE events_day_1
ADD CONSTRAINT events_day_1_event_time_check
snacktime wrote:
I'm working through the architecture design for a new product. We
have a small group working on this. It's a web app that will be using
ruby on rails. The challenge I'm running into is that the latest
conventional wisdom seems to be that since obviously databases don't
scale
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Goboxe
Sent: Monday, October 01, 2007 11:26 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Partitioned table limitation
On Oct 2, 1:38 am, [EMAIL PROTECTED] (paul rivers
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Goboxe
Sent: Monday, October 01, 2007 2:18 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Partitioned table limitation
Hi,
Are there any limitations on number of child
On 08/14/07 14:34, Kenneth Downs wrote:
Tom Lane wrote:
Kenneth Downs [EMAIL PROTECTED] writes:
Speaking as an end-user, I can give only one I've ever seen, which is
performance. Because of MVCC, Postgres's write performance (insert
and update) appears on my systems to be almost
At risk of putting my foot in my mouth again, greatest() returns null if one
or more expressions are null for Oracle enterprise 9.2.0.7 and 10.2.0.3.
The docs for greatest() don't talk of NULL:
SQL select greatest(1,2,null,3) from dual;
GREATEST(1,2,NULL,3)
SQL
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Pavel Stehule
Sent: Saturday, June 30, 2007 10:37 AM
To: Bruno Wolff III; Pavel Stehule; pgsql-general@postgresql.org
Subject: Re: [GENERAL] greatest/least semantics different between
I believe the spec says nulls are ignored for min/max. Postgres is as far
as I know behaving according to spec.
But I question the original poster's report of Oracle's behavior. I don't
have 9.2.0.8 to test, but on 9.2.0.7:
SQL select f1, case when f1 is not null then 'not null' else 'null'
Er ... your example doesn't actually seem to involve greatest() or
least()?
So sorry, it's been a long day, I misread. Yes, greatest/least definitely
does work on Oracle as the OP said. Apologies again.
---(end of broadcast)---
TIP 4:
Overview:
plpgsql functions seem to ignore partitioning, even with
constraint_exclusion on.
Description:
Version is 8.2.3 on RHEL 4, constraint_exlusion is on. I have an
events table (fw_events) partitioned by an int and a date (fw_id,
fw_date for discussion) following the recommendations
at run time.
For the same reason, stable functions such as CURRENT_DATE must be
avoided.
-Original Message-
From: paul rivers [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 08, 2007 2:40 PM
To: 'pgsql general'
Subject: table partitioning and plpgsql functions in 8.2.3
Overview:
plpgsql
Out of curiosity, which big, expensive enterprise database are you spoiled
by? Many that I support do not allow DDL within an transaction, or if they
allow it, there are many caveats and rules.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ron
I am having difficulty getting SSL-enabled Postgres client
libs working on AIX with either vac or gcc using OpenSSL. SSL from other UNIX
flavors has not been a problem.
Versions in question:
AIX 5.1 on power4
OpenSSL 0.9.8
Postgres 8.1.3
I am not that familiar (yet) with the
Try factoring the connect time out of the test. My experience is the
connect is more expensive for Postgres than MySQL. With that out of the
way, I'd wager the times will be closer.
Regards,
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Antimon
39 matches
Mail list logo
