Bruce Momjian wrote:
If someone wants to create a separate web page to track fixes related to
CVE number, that is fine. My guess is that most people reading the
release notes don't care about the CVE numbers themselves (just that
each release has all known security bugs fixed), and most bugs
select 1 from tab having 1=1;
returns 2 rows
I'm curious whats in those two rows... {{1} {1}} ?
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the 8.4.3 binary tarball for solaris sparc
64bit on postgresql.com was shipped with the 32bit includes and the
Makefile fragments from 8.4-community/lib/64/pgxs/src/
I'm specifically hitting this contradition:
$ grep FLOAT8 include/server/pg_config.h
#define FLOAT8PASSBYVAL false
and
$
Bjorn Munch wrote:
I will have a look into it.
as of right now, I suspect what I need are the following files from a
recent Solaris 64bit build...
include/server/pg_config.h
lib/64/pgxs/src/Makefile.global
there are a few more files that could be involved, but AFAIK, they are
feng tian wrote:
Hi,
I want to load balance a postgres server on 4 physical machines, say
127.0.0.11-14. I can set up a pgbouncer on 127.0.0.10 and connection
pooling to my four boxes. However, the traffic from/to clients will
go through an extra hop. Another way to do this, is to send
On 11/27/12 2:41 PM, Tom Lane wrote:
Tweaking the casting rules could have a lot of
unforeseen consequences.
understatement of the year. IMHO. $0.02 worth etc.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql
On 12/5/2012 1:42 AM, Simon Riggs wrote:
I think we need a parameter called
schema_change_reporting = off (default) | on [USERSET]
which displays relevant statistics/reports about the actions taken by
DDL statements. That will also highlight locks and the need to reduce
their lock levels.
On 12/20/2012 12:26 AM, Gavin Flower wrote:
CREATE TABLE test (id int, int sub, text payload);
CREATE INDEX test_idx1 ON test (id, sub);
CREATE INDEX test_idx2 ON test (id);
Nowtest_idx2 is logically included intest_idx1, but if the majority of
transactions only query onid, thentest_idx2
On 12/20/2012 4:17 AM, Brett Maton wrote:
It appears that procpid has been renamed to pid at some point, also
the column current_query appears to have been shortened to query.
My patch updates a couple of queries to use the new shorter column names.
IMHO, any such fix should check the
On 1/7/2013 1:10 AM, Simon Riggs wrote:
On 7 January 2013 07:29, Takeshi Yamamuro
yamamuro.take...@lab.ntt.co.jp wrote:
Anyway, the compression speed in lz4 is very fast, so in my
opinion, there is a room to improve the current implementation
in pg_lzcompress.
So why don't we use LZ4?
On 1/7/2013 2:05 AM, Andres Freund wrote:
I think there should be enough bits available in the toast pointer to
indicate the type of compression. I seem to remember somebody even
posting a patch to that effect?
I agree that it's probably too late in the 9.3 cycle to start with this.
so an
On 1/11/2013 6:56 AM, Steve Singer wrote:
If someone else in the community is running PostgreSQL on AIX then it
would be good if they setup a buildfarm member, perhaps with a more
recent version of AIX.
I am and I'd love to, however, sigh, its deep behind corporate firewalls
and any attempt
On 1/20/2013 9:23 PM, Vivek Singh Raghuwanshi wrote:
3.RedHat_RHEL-6
uuid-devel (Now RedHat is not providing this rpm)
you sure about that? now, I'm running CentOS 6 not RHEL6, but the
packages are 1:1 and built from the same SRPMs.
uuid-devel.i686
1.6.1-10.el6
On 1/23/2013 8:32 PM, Tom Lane wrote:
FWIW, in Fedora-land I see:
F16: 2.1.6 (F16 will go out of support next month)
F17: 2.1.10 (F17 has been stable for 6+ months)
F18: 2.1.12 (F18 just went stable)
While requiring 2.1.10 today might be thought a tad leading-edge,
will that still
RAC, where the masters share a
coherent cache and implement global locks.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
internals.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it to the database encoding and generate an error on any invalid
character. this translation could be identity (eg, UTF8-UTF8)
whereupon it would just validate.a 2nd function would do the same,
but replace errors with the substitution character in the target charset
and not error.
--
john r pierce
have that.
me thinks this would be extremely useful for importing 'dirty' data.
that or a per-connection flag (or option on the COPY command?) that
said substitute-on-error for the likes of UTF-8 imports from CSV.
--
john r pierceN 37, W 122
santa cruz ca
BSD's, Solaris, AIX, OSX, and MS Windows are all platforms
PostgreSQL runs on.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
certainly has
libssl3.so, etc as references. ditto the postmaster/postgres main
program has libssl3.so too. maybe your certificate chains don't come
pre-built, I dunno, I haven't dealt with that end of things.
--
john r pierceN 37, W 122
santa cruz ca
should be with something that is common knowledge,
not something even more obscure than the primary subject matter.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers
finished processing) and this
makes them much easier to follow. Statement level TRIGGERs can be used
for audit logs and similar operations which need to run once per
statement.
as a relative novice, I concur, this is clear, concise, and to the point.
--
john r pierceN 37, W
On 11/04/12 11:59 AM, Jeff Davis wrote:
Is there any fundamental or philosophical reason why a foreign table
can't accept arguments? Should that be a TODO?
what does that even mean?how would 'data' accept 'arguments' ??!
--
john r pierceN 37, W 122
santa cruz
for this?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
hardware, file system, etc.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
25 matches
Mail list logo
