On Thu, Jun 23, 2011 at 7:14 PM, Rodrigo E. De León Plicet
rdele...@gmail.com wrote:
Here:
http://cglendenningoracle.blogspot.com/2011/06/oracle-vs-postgres-postgresql.html
Any comments?
That is quite possibly one of the most ignorant opinion pieces I've
ever read. The janitor in Dilbert is
If #1 was solved by using the raid approach, what happens if one of
the disks containing one of my table spaces crashes.
if you are using raid, your tablespaces are on raid volumes comprised of
2 or more drives, any one of those drives may fail, and the full data is
still available. if you
Eduard-Cristian Stefan wrote:
I have PostgreSQL 9.0.4-1 running as a service on Windows XP Home
Edition,
with the command line of the service being:
D:\me\usr\PostgreSQL\bin/pg_ctl.exe runservice -N pgsql -D
d:/me/etc/PostgreSQL
In the postgresql.conf file I have the following
Stephen Frost wrote:
I love how he finishes with the claim that Oracle keep their finger on
the pulse of where IT is headed, right after admitting that their
client is actually a huge piece of junk.
I guess that was just a typo.
Shouldn't it read [Oracle can] keep their fingers on the throat
I love how he finishes with the claim that Oracle keep their finger on
the pulse
presumably, he means, the jugular ...
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-general mailing list
On 06/23/2011 09:37 AM, Natusch, Paul wrote:
I have an application for which data is being written to many disks
simultaneously. I would like to use a postgres table space on each
disk. If one of the disks crashes it is tolerable to lose that data,
however, I must continue to write to the
On 06/23/2011 10:28 PM, Stephen Frost wrote:
I love how he finishes with the claim that Oracle keep their finger on
the pulse of where IT is headed, right after admitting that their
client is actually a huge piece of junk.
Oracle is able to keep their finger on the pulse of their
On Friday 24. June 2011 03.14.39 Rodrigo E. De León Plicet wrote:
Here:
http://cglendenningoracle.blogspot.com/2011/06/oracle-vs-postgres-postgresq
l.html
Any comments?
I think he got a point in «Oracle as the second largest software company in
the world» which is a killer argument from
Le jeudi 23 juin 2011 à 18:14 -0700, Rodrigo E. De León Plicet a écrit :
Here:
http://cglendenningoracle.blogspot.com/2011/06/oracle-vs-postgres-postgresql.html
Any comments?
There is a previous post by the same author :
Sorry for the late reply - but I still haven't found a solution,
for example I have a PHP script with 5 consecutive SELECT
statements (source code + problem described again under:
http://stackoverflow.com/questions/6458246/php-and-pgbouncer-in-transaction-mode-current-transaction-is-aborted
On 06/23/2011 09:37 PM, Natusch, Paul wrote:
I have an application for which data is being written to many disks
simultaneously. I would like to use a postgres table space on each disk.
If one of the disks crashes it is tolerable to lose that data, however,
I must continue to write to the other
On Friday 24. June 2011 06.01.31 Greg Smith wrote:
The idea that PostgreSQL is reverse engineered from Oracle is
ridiculous.
Maybe he believes that SQL was invented by Oracle?
regards, Leif
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
I would just like to add my voice to those praising the community
support provided by this list.
I am not a DBA, and merely tinker with a few databases, mostly on the
web. As such, my questions have occasionally bordered on the very
silly, but I have always had them answered courteously,
Hi Michael-san.
Sorry very late reaction.
Although it is several years ago, I did the work origin of OSSP-UUID on
windows platform with Ralf-san. He is Great developer!.
http://www.ossp.org/pkg/lib/uuid/
However, I made the mistake in patch then
After late, correction patch was made
On Thursday, June 23, 2011 6:18:18 pm David Johnston wrote:
Also, is this coercion noted in the documentation anywhere? I looked in
the obvious locations (Data Type, Function, Appendix B). There should
probably be something obvious, in the Data Type section, like:
When a Time Stamp with
Hello,
need help,
Declare @TypeTransactionID As int;
Select @TypeTransactionID=ID from TypeTransaction Where TypeTransactionCode
= 'TxnBackupInc' ;
these is in sqlserver. If i want to do same in postgresql then ???
--
Thanks Regards,
Jignesh Ramavat
Software Engineer
On Thursday, June 23, 2011 02:46:52 pm you wrote:
On 6/23/11 3:24:12 AM, Aritz Dávila wrote:
Hi list,
I have installed postgresql 8.4 on Ubuntu server 10.4. I would like to
have remote access to this database so after reading I found out that
modifying pg_hba.conf and postgresql.conf
Hi all!
Sorry for sending this message here, but I couldn't find a better
place after asking in the pgfoundry support forum and not receive any
answer. As it is full of spam, I don't know if it is being read very
often.
Here is my problem:
when I access Npgsql bugs tracker, I get the following
Hello
2011/6/24 Jignesh Ramavat ramavat.jign...@gmail.com:
Hello,
need help,
Declare @TypeTransactionID As int;
Select @TypeTransactionID=ID from TypeTransaction Where TypeTransactionCode
= 'TxnBackupInc' ;
these is in sqlserver. If i want to do same in postgresql then ???
you can't
On Fri, Jun 24, 2011 at 3:41 AM, Jignesh Ramavat
ramavat.jign...@gmail.com wrote:
Hello,
need help,
Declare @TypeTransactionID As int;
Select @TypeTransactionID=ID from TypeTransaction Where TypeTransactionCode
= 'TxnBackupInc' ;
these is in sqlserver. If i want to do same in postgresql
On Fri, 24 Jun 2011 10:16:52 -0500, Merlin Moncure
mmonc...@gmail.com wrote:
http://www.postgresql.org/docs/9.0/static/plpgsql.html
http://www.postgresql.org/docs/9.0/static/plpgsql-declarations.html#PLPGSQL-DECLARATION-PARAMETERS
Plus http://www.postgresql.org/docs/current/static/sql-do.html
On 06/23/2011 02:45 PM, David Johnston wrote:
...
As for Time handling has lots of subtleties that take time to digest; a
good programmer and API do their best to minimize the number of hidden
subtleties to be learned
I meant that time-calculations themselves have lots of issues and
As I understand it, documentation patches are welcomed:)
I'd indeed wish some radical changes to the documentation.
To start with, the fundamental data type names are rather misleading; SQL
standard sucks here, true, but Postgresql also has its idiosincracies, and
the docs do not help much:
Yeah, although cheap contribution by me.:-)
Thanks!
(2011/06/25 2:10), Michael Gould wrote:
Thanks for the reply. We're using Windows 32 of Postgres in
development but
would like to deploy windows 64 when we are ready. I agree, I think that
Postgres ought to provide fully support for
On Wed, 2011-06-22 at 16:17 +0100, Thom Brown wrote:
On 13 May 2010 18:28, Guillaume Lelarge guilla...@lelarge.info wrote:
Le 13/05/2010 19:24, Thom Brown a écrit :
On 13 May 2010 17:49, Guillaume Lelarge guilla...@lelarge.info wrote:
Le 13/05/2010 14:12, Thom Brown a écrit :
On 5 March
OpenSuse 11.4 x86-64
gmake install builds and places the requisite pieces as expected.
Running
psql --username postgres -d postgres -f xml2--1.0,sql
results in
psql:xml2--1.0.sql:8: ERROR: function xml_valid already exists
with same argument types
psql:xml2--1.0.sql:12: ERROR:
Dne 20.6.2011 18:47, Alexander Farber napsal(a):
isn't having prepared statements good for overall performance?
I've already mentioned that in my previous post, but let's make this
clear. Prepared statements are good for performance, but only if you're
going to execute the statement multiple
On 06/24/11 4:51 PM, Tomas Vondra wrote:
And there's a downside too - with prepared statements the the planner
can't use the actual parameter values to choose the plan (it does not
know them), so it may choose a plan that's good on average but sucks for
some parameter values.
indeed, this can
Dne 25.6.2011 02:15, John R Pierce napsal(a):
indeed, this can really bite you on partitioned tables.My lead
Oracle programmer would like to see support for prepared statements that
are parsed but not preplanned... our standard coding model has all the
queries prepared up front as part of
29 matches
Mail list logo
