o the new system. You
really haven't given us much information on what problem you are having.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-gen
PostgreSQL cluster".
The big problem was that the title said "Install pg_upgrade", but the
detail had you installing two things, one of which was pg_upgrade. It
was using pg_upgrade in both a generic sense, and in the
/contrib/pg_upgrade sense, which is bound to confuse, as you sai
x27;mit';
> oid | relname
> +
> 3000767630 | company
> 3000767633 | company_history
> (22 rows)
>
Interesting. Odd it would report the max 32-bit signed int. I wonder
if it somehow is getting set to -1. I looked briefly at the pg_upgrade
code and it a
t; I think C90 and C99 specify different behaviors with atol
>
> Is there some standard way postgresql parses integer strings? Maybe that
> method should be used instead of duplicating the functionality so at least
> the two behave consistently.
>
> --brian
>
> On Sep
Bruce Momjian wrote:
> Brian Hirt wrote:
> > It looks like it's related to atol
>
> Yep, I found the use of atol in the pg_upgrade code too. Working on a
> patch now.
I have applied the attached patch to HEAD and 9.0.X. Odd I had never
received a bug report about this
Brian Hirt wrote:
> Bruce,
>
> The applied patch has the same behavior on i686 Ubuntu 10.04. It
> looks like atol() is just a macro for strtol() in stdio.h. I think
> you want strtoul() instead of strtol()
Yes, thanks. I have now applied that fix in HEAD and 9.0.X.
> when
> space in the db as it does in a flat file. that's just an
> approximation. The actual size of each type etc is defined in the
> other links in this thread.
Folks, we have an FAQ about this:
http://www.postgresql.org/docs/faqs.FAQ.html#item4.5
--
Bruce Momjia
e pg_dump should disable
> >> statement_timeout when it runs.
> >
> > You mean like this?
> >
> > http://archives.postgresql.org/pgsql-committers/2008-05/msg00026.php
>
> Very cool. I assume it's not in 8.3.3 then?
No, because this is a functionality change, rather than
t;
>
> On Windows XP, however, there is no Control Panel applet for ODBC
> management. The answer should read:
>
> "Go to Programs -> Administrative Tools -> Data Sources and Add the
> PostgreSQL Unicode driver".
Uh, I am not sure where you saw this FAQ but
Alvaro Herrera wrote:
> Bruce Momjian escribi?:
> > Dan Dascalescu wrote:
> > > I'd like to submit a correction for question "2.1) How do I setup a
> > > datasource?" in the FAQ. The existing text reads:
> > >
> > > "For Windows, us
size_t not int, but I have a feeling there are a lot of other similar
> gotchas when running this code on a 64-bit machine. We use int
> arithmetic an awful lot for stuff that probably should be size_t
> or ssize_t ...
I assume this is not a TODO item.
--
Bruce Momjian <[EMAIL
ill executed. Kill was never officially supported as a way to
terminate a backend, but it will be in 8.4 and there is an SQL function
to do it too.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your
is complicated... it's obviously
> used for a lot of other things... could you use another character?
I think a search for ' -' will show you the items you want.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
Russ Brown wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruce Momjian wrote:
> > Scara Maccai wrote:
> >> Hi,
> >>
> >> I was looking at the TODO:
> >>
> >> http://www.postgresql.org/docs/faqs.TODO.html
> >>
ing and the other is using the timezone meaning.
>
> We don't have much control over the zone definition, so I'm thinking
> maybe the abbrev should be removed from the tznames lists. But that
> seems a bit sucky too. Does anyone have any idea if the zic folk would
> be respo
gging every single query. By
> the way, I'm using Postgresql 8.3.1 on window xp.
>
> Am I doing something wrong?
The problem is that the checks for the statement type are done at the
time the query arrives from the client, not while executing in a
function.
--
Bruce Momjian <[EMAI
and
> ignore inserts.
No, sorry.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-general mailing list (pgsql-general@pos
d optimize this into
> something fast enough to be usable; but it's a research problem.
> (The cases that I can see how to optimize are pretty much equivalent to
> plain foreign key constraints, anyway.)
Is this a TODO? I assume it is not.
--
Bruce Momjian <[EMAIL PROTECTED
| f| f | |
| {search_path=asdf}
(2 rows)
The ALTER SET command is performed; it only generates a NOTICE. Is
that the problem?
(FYI, you emailed the Postgres general _owner_; that is not the right
address for posting questions.
server logs or kernel logs show anything unusual?
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-general mailing list (pgsql-gener
any serious discussion with encryption starts here)
> *) other things you can do with function source besides encryption
>
> for example, take a look at one idea I had (not at all vetted, but a start):
> http://archives.postgresql.org/pgsql-performance/2007-12/msg00337.php
>
> me
> C is not magic obfuscation gear. Anybody with a debugger can expose
> what it's doing. There have been math papers showing that it's
I bet 'strings' shows all the SQL queries in a C object file too.
--
Bruce Momjian <[EMAIL PROTECTED]>http
c patch that may clear up some of the confusion.
Thanks, patch applied.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsq
it's output whether or not it
> should allow a particular action.
We were just talking today about adding column and row-level security to
Postgres 8.4:
http://archives.postgresql.org/pgsql-hackers/2008-09/msg01654.php
--
Bruce Momjian <[EMAIL PROTECTED]>http:/
ate or leave the behavior unchanged.
Personally I think immediate makes more sense because issuing
pg_start_backup() seems like it should behave like a manual CHECKPOINT
command.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB h
s there a way to avoid this problem without having to reset all passwords
> or storing them in plain text?
I don't know of a way to make MD5 and db_user_namespace work cleanly so
we are considering removing db_user_namespace in 8.4.
--
Bruce Momjian <[EMAIL PROTECTED]>
Alvaro Herrera wrote:
> Tom Lane escribi?:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > I don't know of a way to make MD5 and db_user_namespace work cleanly so
> > > we are considering removing db_user_namespace in 8.4.
> >
> > We are? It
t the backup module
> should be ready to handle these situations in the future.
No, I have no suggested workaround.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive,
>> detect other processes attached to a shmem block.
>
> > Didn't we solve this problem on Windows?
>
> Not terribly well --- see active thread on -hackers.
We could allocate a small shared memory area to solve this and use
mmap() for the other shared memory usage.
--
ain
> precise info on the error type).
>
>
> > That feature alone can help you enormously. Lest you think I'm
> > biased, I dba a mysql box professionally...every time I pop into the
> > mysql shell I feel like I'm stepping backwards in time about 5 years.
>
>
>
> > Out of curiosity, what language are you using?
>
> For MySQL I've been mostly using PHP, occasionally Java, Python and C.
Interesting. I think we need to decide if we want a TODO for this.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.
y" going to the list and some have
"reply" going to the author, I would have to think about the right reply
option every time I send email.
Fortunately, every email list I subscribe to and manage behaves like the
Postgres lists.
--
Bruce Momjian <[EMAIL PROTECTED]>
I have installed.
Am I mising something here, or could the #ifdefs have something to do
with it not picking up the newer ossp uuid defnitions?
Any suggestions would be greatly appreciated.
Thanks
Bruce
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to
bin76784 Oct 28 15:33
/usr/lib/libuuid.so.16.0.22
Do I need to use a specific version of the ossp-uuid libraries for this
module?
Thanks
Bruce
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>
> Huh. Nothing obvious in your info about why it wouldn't work. I think
> you'll need to dig through the config.log output to see why these link
> tests are failing. (They'll be a few hundred lines above the end of the
> log, because the last part of the log is always a dump of configure's
>
>
> The 1.6.2 stable version which you use is right.
>
Thanks, we managed to get it working now. Thanks for the pointers.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>
> Bizarre ... I've never heard of a Unix system that didn't consider that
> a default place to look. Unless this is a 64-bit machine and uuid
> should have installed itself in /usr/lib64?
>
It is a rather peculiar issue, I also assumed that it would check the
standard locations, but I thought
t have the
full page write copies of those pages to restore, and the compressed
operating system might not be able to guarantee that the other parts of
the file will be restored if only part of the 512 gets on disk.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Enterprise
e we want streaming archive logs, but there are still
going to be people who are archiving for point-in-time recovery, and I
assume a good number of them are going to compress their WAL files to
save space, because they have to store a lot of them. Wouldn't zeroing
out the trailing byte
rm that this is the case?
Yes, "random" means random.
> Is this really a good idea? Is non-deterministic behavior really
> acceptable? I would think it would be much more sensible to have it
> operate deterministically (such as with some predetermined random
> sequence of numbers used re
lem.
>
> If the INSERT fails, the SERIAL is in any case increased...
>
> So this was the reason, why I have tried to use max(serno) and add +1
> the get the next value for "serno".
>
> Is there a solution for it?
You should read our three FAQ entries about
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Tom Lane escribi?:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > I don't know of a way to make MD5 and db_user_namespace work cleanly so
> > > > we are considering removing db_user_na
etting email
help from us.
Michelle is asking to be involved in this community and there are
requirements for that involvement.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard d
#x27;ret' in function
> readdir
> Error E2451 ..\..\port\dirent.c 109: Undefined symbol 'handle' in
> function closedir
> Error E2451 ..\..\port\dirent.c 110: Undefined symbol 'handle' in
> function closedir
> Error E2451 ..\..\port\dirent.c 111: Undefined sym
hing in the developer docs regarding them. Does that mean
> they
> won't make it or that simply the documentation isnt't yet there?
The patch is still being reviewed for inclusion in 8.4.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
Thomas Kellerer wrote:
> Bruce Momjian wrote on 20.11.2008 22:56:
> >> From http://umitanuki.net/pgsql/wfv08/design.html I got the impression
> >> that
> >> windowing functions will make into (at least partially) into 8.4 because
> >> on that
> &
d. I am going to post
another blog tomorrow with more thoughts.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-gene
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> So, to a first approximation, the PG list traffic has been constant
> >> since 2000. Not the result I expected.
>
> > I also was confused by its flatness. I am finding
brian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >>
> >> I am finding the email traffic
> >> almost impossible to continue tracking, so something different is
> >> happening, but it seems it is not volume-related.
&g
Steve Crawford wrote:
> Bruce Momjian wrote:
> > brian wrote:
> >
> >> Tom Lane wrote:
> >>
> >> Perhaps it's just subjective: we're all getting older.
> >>
> Which, as "Dr. A" (aka Isaac Asimov) pointed ou
Ron Mayer wrote:
> Joshua D. Drake wrote:
> > On Fri, 2008-11-21 at 08:18 -0800, Ron Mayer wrote:
> >> Bruce Momjian wrote:
> >>> Tom Lane wrote:
> >>>> ... harder to keep
> >>>> up with the list traffic; so something is happening that a
Magnus Hagander wrote:
> Bruce Momjian wrote:
> > Ron Mayer wrote:
> >> Joshua D. Drake wrote:
> >>> On Fri, 2008-11-21 at 08:18 -0800, Ron Mayer wrote:
> >>>> Bruce Momjian wrote:
> >>>>> Tom Lane wrote:
> >>>>>>
othing for backbranches.
>
> So, if you can be a bit more specific in what you want :) Attached is
> for example "commits per month" and "lines per month".
Yea, this is the graph I was looking for; unfortunately it does not
shed any insight on why things seems busier;
rs ago when the default table type did not have
> transactions and subqueries were not existent. The features I was
> looking for were already in PostgreSQL for several versions.
>
> I am surprised to see such an honest post regarding MySQL.
Monty is quite suppor
described.
Yes, \dt was designed that way, and *.name is the proper way to show
tables in all schemas.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be you
t about why there is no interval_abs(): it is unclear what
value to return:
http://archives.postgresql.org/pgsql-general/2009-10/msg01031.php
http://archives.postgresql.org/pgsql-general/2009-11/msg00041.php
--
Bruce Momjian http://momjian.us
a password, which is the most basic way to go if
> you don't have a keystore to use.
I covered this a little bit in my recent security presentation:
http://momjian.us/main/presentations.html#securing
--
Bruce Momjian http://momjian.us
EnterpriseDB
to see the inserts or updates since these may
> have sensitive data like credit card data which I don't want logged in
> the logs. I really don't even care if the SELECT was successful or not,
> or what the results of the SELECT were.
No, log_statement doesn't allow d
Kern Sibbald wrote:
> Hello,
>
> Thanks for all the answers; I am a bit overwhelmed by the number, so I am
> going to try to answer everyone in one email.
We aim to please, and overwhelm. :-)
--
Bruce Momjian http://momjian.us
EnterpriseDB
roplang: language removal failed: ERROR: cannot drop language plpgsql
because it is required by the database system
I assume we still want to allow the language to be uninstalled, for
security purposes. Right? Any suggestions?
--
Bruce Momjian http://
Tom Lane wrote:
> Bruce Momjian writes:
> > One problem is that because system oids are used, it isn't possible to
> > drop the language:
> > I assume we still want to allow the language to be uninstalled, for
> > security purposes.
>
> Yes. That behavior i
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > Bruce Momjian writes:
> >
> >> One problem is that because system oids are used, it isn't possible to
> >> drop the language:
> >> I assume we still want to allow the language to be uninstall
LANGUAGE plpgsql;
ALTER PROCEDURAL LANGUAGE plpgsql OWNER TO postgres;
What is odd is that I used the same process that initdb uses to create
other objects. Does anyone know why this is happening?
--
Bruce Momjian http://momjian.us
EnterpriseDB
do this
> in initdb, filling in template0:
> CREATE EXTENSION plpgsql ...;
>
> Then at createdb time, what would become automatic is:
> INSTALL EXTENSION plpgsql;
>
> And that's it. pg_dump would now about extensions and only issues this
> latter statement in its dump.
>
Tom Lane wrote:
> Bruce Momjian writes:
> > I installed PL/pgSQL by default via initdb with the attached patch. The
> > only problem is that pg_dump still dumps out the language creation:
> > CREATE PROCEDURAL LANGUAGE plpgsql;
> > ALTER PROCEDURAL LANGUAG
ere has been no work done that would
> make it any more reliable for 8.5.
I do not share Tom's conclusions.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup.
fined array data type
o a user-defined enum data type
So, pg_migrator is a work in progress. It current requires migration
testing and should be used by experienced Postgres users. Someday
pg_migrator will be easier to use and more reliable.
--
Bruce Momjian http://momjian.
Bruce Momjian wrote:
> pg_migrator (not pg_upgrade) has been used by many people to migrate
> from 8.3 to 8.4. I just helped someone yesterday with a migration.
> pg_migrator threw an error because they had reindexed pg_largeobject,
> and pg_migrator was not prepared to handle that
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > I installed PL/pgSQL by default via initdb with the attached patch. The
> > > only problem is that pg_dump still dumps out the language creation:
> > > CREATE PROCEDURAL LANGUAGE plpgsq
Phoenix Kiula wrote:
> On Fri, Dec 18, 2009 at 3:54 AM, Bruce Momjian wrote:
> > Bruce Momjian wrote:
> >> pg_migrator (not pg_upgrade) has been used by many people to migrate
> >> from 8.3 to 8.4. ?I just helped someone yesterday with a migration.
> >> pg_migr
A. Kretschmer wrote:
> In response to DM :
> > Hello All,
> >
> > When is the release date for Postgres 8.5?
>
> Never.
>
> The next version will be 9.0, released when it is ready for production.
Yea, we are months away from a new major release.
--
Bruce M
ort answer is
that there is no different for any of them in any areas, except
documented behavior, e.g. char(10) is always output as 10 characters.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Chris
plus toast items. It would be a
> bit slower, but the normal case of using the same server version would
> be fast.
Added to TODO:
Consider showing TOAST and index sizes in \dt+
* http://archives.postgresql.org/pgsql-general/2010-01/msg00912.php
--
Bruce Momjian http://momjia
the 'not null' -
> constraint are in the child-table, in other case they are not.
>
> Version 8.4.2.
>
> Bug, feature? What have i overlooked?
>
>
> Andreas
> --
> Andreas Kretschmer
> Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> H
nt
> > the
> > doc link.
>
> http://www.postgresql.org/docs/8.4/interactive/storage.html
>
> Read there and the sub-chapters.
Yea, "base" was chosen because that makes the directory hierarchy
"/data/base", e.g. "database".
--
Bruce Momj
drant Baltimore, MD
> PostgreSQL Training, Services and Support
> g...@2ndquadrant.com www.2ndQuadrant.com
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pg
es of writes of byte sequences to
> offsets within files in the cluster. A new cluster (or a new
> database created in the original cluster by CREATE DATABASE)
> will have a different layout in its files, so the WAL archives
> don't mak
ng,
> query characteristic, etc.)?
> Is there any feedback showing the feature kicking in (e.g. an explain
> analyze output, log, etc.)?
The feature is called 'synchronize_seqscans' and was implemented in
Postgres 8.3.
--
Bruce Momjian http://momjian.u
urrent client encoding,
> > even
> > if the data does not pass through the client but is read from or
> > written to a file.
> >
> > Seems clear enough to me.
> >
> > regards, tom lane
>
> Maybe the link might help?
>
gresql.org/pgsql-general/2003-07/msg01448.php
>
> I think, this is a bug, isn't it?
Yep, added to TODO:
Allow \dd to show constraint comments
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://ww
Tom Lane wrote:
> Bruce Momjian writes:
> > I have updated the documentation to be more direct about COPY encoding
> > behavior. Patch attached and applied.
>
> Uh, why exactly do you find that better? "Processes data" seems a lot
> vaguer to me than the pr
Peter Headland wrote:
> In respect of Bruce's proposed changes, I prefer the original wording
> (for the same reasons as Tom), but with the addition of the mention of
> the server - "... read from or written to a file directly by the
> server".
OK, done with the a
eople have been bit by this, then maybe ... comments anyone?
I have applied the attached documentation patch to subtly mention this
issue.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/co
> ***
> *** 437,442
> --- 511,524
> CurrentLocaleConv.n_sign_posn = extlconv->n_sign_posn;
>
> /* Try to restore internal settings */
> + #ifdef WIN32
> + #undef strdup
> + if (lc_ctype_change)
> +
Tom Lane wrote:
> Bruce Momjian writes:
> > Where are we on this issue?
>
> According to my files, I complained about the extreme ugliness of the
> patch (redefining strdup for pete's sake) and the fact that it did not
> actually do things anything like the LC_TIME code
Tom Lane wrote:
> Bruce Momjian writes:
> > Right, but you are saying it is still an open issue, which says we
> > should look at it.
>
> Sure. Maybe put it on TODO?
OK, TODO is:
Fix locale-aware handling (e.g. monetary) for specific
server/client
Hiroshi Inoue wrote:
> Bruce Momjian wrote:
> > Where are we on this issue?
>
> Oops I forgot it completely.
> I have a little improved version and would post it tonight.
Ah, very good. Thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB
Hiroshi Inoue wrote:
> Bruce Momjian wrote:
> > Hiroshi Inoue wrote:
> >> Bruce Momjian wrote:
> >>> Where are we on this issue?
> >> Oops I forgot it completely.
> >> I have a little improved version and would post it tonight.
> >
> >
l if the schema does not exist
Hmm. Well, it says TABLE IF EXISTS, not TABLE AND SCHEMA IF EXISTS.
;-)
Not sure if it makes sense to change it.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.c
Chris Roffler wrote:
> Are there any guidelines for XML performance tuning ?
Uh, no, I have never seen any.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010
red, for easy and performant redirection of just my
> logged statements?
Our logging system is very flexible, but not work-free on the user end.
I don't see us changing things in that area.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://
Greg Sabino Mullane wrote:
> Bruce replied:
> ...
> >> This means that, even using syslog as a destination, it's not possible for
> >> me to filter statements without some sort of log-text parsing, which I'd
> >> prefer to avoid on effort, performance and
Stuart Bishop wrote:
-- Start of PGP signed section.
>
>
> On Wed, Mar 10, 2010 at 8:51 AM, Bruce Momjian wrote:
> > Greg Sabino Mullane wrote:
> >> Bruce replied:
> >> ...
> >> >> This means that, even using syslog as a destination, it&
Also, you can do:
NET USER postgres /delete
as an administrator.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
--
Sent via pgsql-general mailin
t seems we have a
clear consensus on this and we should document this.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
--
Sent via pgsql-general mailing list (p
; core xml support in the manuals or anywhere in the net.
We have fixed the serious bugs in /contrib/xml2 with the minor releases
that came out today, 2010-03-15.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.en
Greg Smith wrote:
> Bruce Momjian wrote:
> > Greg Smith wrote:
> >
> >> Given what you've said about your budget here, I suspect that you're
> >> heading toward either 3ware or LSI and all SATA drives. I wouldn't
> >> expect that bi
nd if so, what is it? If it was rejected due to some
> filter, it would be desirable (and polite) if the recepient was told what
> happened.
The bottom line is that this email list is best at answering short,
detailed questions. Larger questions that require a lot of analysis by
reader
> - is there any options that can be set in postgres libpq C library to
> > prevent the connection functions to search for password in files ?
>
> No, but you could possibly set the PGPASSFILE environment variable to
> a place where you *know* there won't be a pgpass file, if
t it). So that
> pretty much kills any thought that it might've once worked and we just
> forgot.
I have removed the Amiga support mention for Postgres from Wikipedia:
http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems#Operating_syst
601 - 700 of 2119 matches
Mail list logo