fire
and all those other tables need to be updated too.
> However, if that fails, the table is dead. You will have to reload it from
> backup.
Right, and that goes for all the affected tables.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing l
g
cutover period).
This second approach isn't faster, it's hard on I/O and disk space,
but it keeps you up and you can do the changes at a leisurely pace.
Just make sure you have the I/O and space before you do it :)
Hope that helps,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mai
ntributors to Postgres, who
appear to work mostly in a mode where email makes things easy for them
and logging into a new forum tool makes things harder.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make change
-- that requires no trades.
Distributing data reliably with ACID semantics and no data loss or
corruption or loss in write throughput is not possible, at least
today. You have to pick which poison you want :)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing lis
if the transaction failed half way through
because it turns out there's nowhere to put the data I've just staged.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ng 9.2.
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ace the critique in its own terms.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
bility historically was the basis for something
becoming a major version upgrade. (I can recall a couple bugs where
you had to tickle the catalogues, so it's not exactly true that
they're never incompatible, but it's incredibly rare.)
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via
f arrogance.
Nothin' for nothin', but I don't think it helps Postgres to attack
others' business plans -- whatever one thinks of them -- as part of an
argument about why Postgres is the right tool for a given job.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-gene
mysql2pgsql conversion rather than N dedicated small teams for
> every mysql client out there.
…I don't think anyone is telling you, "Don't build this." You should
do what you like with your time :)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgs
MySQL, MySQL always wins, what you teach them is
"Postgres performance sucks."
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
g to have to accept, however,
and that's that there are way more application coders than there are
people who really get database systems. Fixing this problem requires
years of efforts.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@pos
been in the
sort of long, boring speculative conversation that could have been
shut down quickly with this kind of data.)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
message that data is committed before any replication of the
data has commenced," would that help?
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
egards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
…
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/postgresql/Driver
… since it can't find the driver, I'd bet that your classpath doesn't
contain /opt/postgresplus/edbmtk/lib.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-gene
ecover after a restart.
It may not be the hardware. Depending on how vmware is configured, it
could just be a setting. Also, something in the OP's message made me
think that this was _actually_ a network-attached disk, which can also
have such problems. (But in general, I agree.)
A
--
And
You may end up taking an outage in effect, because you need to compact
them at least once. If you can flip to a replica, that is the easiest
way to fix it.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to yo
at stuff about what the IETF does some
while ago. There is definitely more than one way to do this.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
you actually want to fail over.
I've seen an awful lot of people want automatic failover who also
can't afford for the already-committed transactions on the master to
be lost. Unless you're running synchronous, be sure you have the
workload that can actually accept lost writes.
A
--
And
logise in case
that wasn't clear.
> It is the perceived intention of what one says that is important, not what
> one actually says!
I think that is perhaps a false dichotomy. But I also think I have
said enough on this topic, so I shall stop now.
Best regards,
A
--
Andrew Sullivan
a..
out it by writing down rules.
Still, the exercise of writing down rules may help to notice things
one wouldn't say to a friend. And I hope we're all friends here.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To m
f slaves.
If someone did that, it would fall under (2), no? (I note that a
recent RFC, of which I am a co-author, about DNS terminology did say
that "primary" and "secondary" were to be preferred over "master" and
"slave". I didn't personally agree with t
l than to try to figure out
whether something is a good idea in the abstract. The shorter and
easier to understand the proposal is, I think, the more useful it is
likely to be.
I hope this was useful. If not, please delete and ignore :)
Best regards,
A
--
Andrew Sullivan
a...@crankycanuc
l so that the session hangs around). Eventually, the Postgres
backend will try to talk to the session and discover it isn't there,
and you'll get a termination logged (assuming you have loging turned
up that high).
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailin
also some firms that can help with
migration if you like.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o satisfy the condition.
Also, of course, there is the application_name (string) parameter. In
principle, you ought to be able to filter on this. Again, won't help
you if your application login is somehow compromised.
I agree that all of this depends on logging everything and filtering,
howeve
ght, sure. The security profiler would still need
to make a list of this fact and then ask how countermeasures mitigate
it.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
d,
you need to know the state of all of it.
For realistic cases, I expect that deleted data is usually more
important than updated data. But a threat modeller needs to
understand all these variables anyway.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list
delete data from a system because
it's been archived somewhere else or something like that -- not all
databases have the totality of all the relevant data in them, but can
often represent just "current" data.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql
consider
trying out the command line. You'll be surprised at the power you get
once the initial learning curve is over.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postg
y and rigour are the changes ;-)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ix prior to a real solution
they'd give you a path.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
. But in general, the experience seems to be
that triggers are easier to get right (novice or no, _pace_ section
38.7).
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
in the table. I don't know what rewriting such a query would
mean.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
that to be useful when talking to Oracle partisans.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
frustrating, but this is not the only
community to have had that issue (cf. Linux kernel, for an
approximately infinite series of examples of this). I am not sure
that the answer to this is a rejigging of the basic development model.
Hard cases make bad law.
Best regards,
A
--
Andrew Sullivan
with crowdsourced editing of job
postings is in any way appropriate for the pgsql-general list.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
all the data from one to the
other. Depending on your uptime requirements and the size of the
database, this approach can either be a life saver or a total waste of
time and will to live. More often the latter, please be aware.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql
and restore locally, you could do
pg_dump -U postgres -h 192.0.2.1 -C egdb | psql -U postgres
I recommend reading the pg_dump (and if you like, pg_dumpall) manuals
before proceeding.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general
by far the most disk space (still somewhat expensive on SSD)!
This doesn't actually solve your problem, but you could mitigate the
cost by putting those tables on spinning-rust disks using tablespaces
or symlinks or whatever.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via
. You should always try to
stay on the latest minor release of your version of Postgres.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
) have this functionality, but I kind of
doubt it since both were designed to get rid of several of the
complexities that Slony presented. (Slony had all those complexities
because it was trying to offer all this functionality at once.)
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
reduced the number of such
cases. Some convenience was lost (I still get tripped up from time to
time, but I'm not doing Pg work every day), but the overall
reliability of things was increased. So I'd say it's probably not a
bug.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql
;
These both work. The problem is, I think, that you have different
rules for when Q2 fails, and without knowing your exact
circumstances I suspect we can't say much more. Indeed, however, it
sounds to me like you think these are in the same workflow, but
they're not.
A
--
Andrew Sullivan
and then
punycode-decoding it doesn't always result in the same label. See my
other message.
Did I mention that IDNA is a mess?
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
, to_idna2008, check_ldh, split_labels, and so on. If this
seems possibly interesting for collaboration, let me know I'll try
to put together the relevant people.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
/libidn2/libidn2/source/0d6b5c0a9f1e4a9742c5ce32b6241afb4910cae1:
It's GPLv3, though, which brings its own issues.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
change only happens twice a year so
nobody _ever_ thinks of it when troubleshooting.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On Tue, Aug 19, 2014 at 07:41:00PM +0530, Sameer Thakur wrote:
We are thinking of building our own version of Oracle's sysdate, in
the form of PostgreSQL extension.
I thought that was the point of the statement_timestamp() function?
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via
that what you have on the
target (backup) machine is in fact production-ready? I guess I don't
really understand what you are trying to do.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
effects.
Hmm. I've _used_ transactions in such files, I'm pretty sure. You
don't need the --single-transaction setting for this, just do the
BEGIN; and COMMIT; yourself.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
On Wed, Jun 25, 2014 at 03:37:11PM +0100, James Le Cuirot wrote:
Sorry, you're missing the point. I'm trying not to alter the existing
behaviour of the Chef database cookbook
Ah, got it. Sorry, I'm clueless. No, I don't think I have a
suggestion, then.
A
--
Andrew Sullivan
)
support in Postgres. Be careful with this, however, as it is easy to
make a system so convoluted that nobody can understand it.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
put that in your
query.
Are you sure you want this without time zone? In my experience,
almost every time people think they want without time zone they
actually don't.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
. If it were me, I'd say yes.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
recent releases (9.1.x certainly
qualifies) you are much better to tune autovacuum.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
; and (3) there _are_ several in-memory-only databases on the
market, including free-software ones, so it isn't clear what Postgres
would contribute, especially since its basic design isn't obviously
amenable to this sort of use.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via
On Tue, Apr 08, 2014 at 12:46:37AM +0200, Stefan Keller wrote:
Hi Andrew
2014-04-07 23:37 GMT+02:00 Andrew Sullivan wrote:
(1) this has been discussed many times in the past (...)
Can you point me to one of these discussions?
Actually, I browsed once again the mailing list
needlessly
in case the user just uses the first page, which IME happens a lot).
Note that even Google doesn't give you an accurate number -- they just
say about ten trillion or whatever.
Hope that's useful,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql
I did this in the past we didn't have window functions, so
I simulated it another way.)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
don't you put a DO INSTEAD trigger or rule (I'd suggest the
former) when you put in a 0 to do nextval() instead on the sequence
for the column?
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
such that it doesn't look
like a deadlock to the detector, but the lock chain is such that no
query will ever be able to release.)
I suspect you need to get your locks in a consistent order or you'll
continue to have this problem.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing
order is an
excellent way to run into trouble, and long-running transactions are a
major source of these problems. Without a more detailed report about
what is going on in the present case, I don't think it's going to be
possible to diagnose better than has been done.
A
--
Andrew Sullivan
wondering if there's a nicer way.
This is probably what I'd do, assuming that further processing isn't
more data transformation. If it _is_, then I'd do the whole thing in
a single step (in the database, once I inserted).
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing
of concurrency.
It _is_ doing the appropriate thing, though: this is SQL. The rows
aren't ordered unless you tell them to be.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
-mail facilities or e-mails sent other than
strictly for business purposes.
--
Andrew Sullivan
a...@anvilwalrusden.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Feb 21, 2014 at 12:14:42AM +0530, Dev Kumkar wrote:
These are the two clients which I have currently who communicate with
database.
Do you control the client code? If so, why not set the TimeZone
locally when you connect? That's the right way to handle this,
really.
A
--
Andrew
TimeZone commands. I think you'll find that the
client can set whatever time zone it wants.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
in the server are not actually in a time zone.
They're all stored as UTC, and the display is altered according to
what your time zone settings are at the time of query.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
will be unusual, but
that really is how it works.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
going to yield the most predictable behaviour for the users, I suspect.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Andrew Sullivan
a...@anvilwalrusden.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription
. This is
strange to people because when you're developing it's normal to think
of functionname(args) as the thing you're changing, but in a system
that allows overloading like Postgres that's not really true for
production.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list
.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
write code that read minds, they'd be
working on more profitable enterprises ;-)
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
out that one of the brilliant developers has not only thought of
it, but has fixed it while you weren't looking. In a large-scale
generalized way that doesn't have whirling knives sticking out of it.
(Yes, I have been using some other DBMSes recently, and no, I don't
like it.)
A
--
Andrew Sullivan
.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
or whatever (I presume they're
not going away because your connection is long lived)? They're
supposed to be temporary, after all: cheap and disposable.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
it could be that a lot of these allocations fit fine in real memory if
only 8 processes are doing it; but if 10 do, you pass your threshold
for physical memory and start swapping. I wouldn't expect high CPU
under that case, though, but high I/O. So I think it's doubtful.
Best regards,
A
--
Andrew
that, unfortunately).
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Jan 03, 2014 at 10:00:42AM -0500, Tom Lane wrote:
know the end-to-end MTU size with any reliability.
Well, you could try PMTU discovery, though I agree that it's not
great. It also seems pretty low-level for something like the DBMS to
be doing.
A
--
Andrew Sullivan
are two ways I've done this sort of thing in the past.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
/listinfo/arin-announce
Please contact i...@arin.net if you experience any issues.
- End forwarded message -
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
() all the input text during searches, in order to avoid any
work on the schema. Bit of a kludge, though.
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
, and I
humbly suggest that your evaluation of convenience in this case is
anyway incomplete.
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
were when you have a crashed or otherwise troublesome system.
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
is
_almost_ but not quite Unicode. This bites people generally in
internationalization.)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
with UTF-8 encoding. I liked your conversion
suggestion, however, in your other mail.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
anyway. I guess I'd respond that you could use TLS
anyway because it would help in case of a network compromise.)
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
is having something done to them.
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
by IBM, whose product once made my afternoon more
amusing than I wanted by blowing up the data area on fail over not
once, or even twice, but three times. (This was attributed to
operator error, because the operator had dared to run the failover
sequence.)
--
Andrew Sullivan
a...@crankycanuck.ca
application to scale to large
numbers of users, you need to avoid application-database round
trips.
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
to be
in some sense under the control of the host. We have roughly 40 years
of experience with these things, and the evidence is that
comprehensive but easy is either badly insecure or very hard to
operate well. Which trade do you want to make?
Best,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent
1 - 100 of 720 matches
Mail list logo
