Peter Eisentraut writes:
> Well, we could make initdb patch it up, but that might seem excessive.
I sometime wonder if archive_mode shouldn't default to "on" with the
archive_command set to either '/bin/true' or 'rem' for windows.
That allows to install proper archiving without restart, but the
On 31.08.2011 16:05, Heikki Linnakangas wrote:
While looking through old emails, I bumped into this:
http://archives.postgresql.org/message-id/25219.1303306...@sss.pgh.pa.us
To recap, setlocale() on Windows is broken for locale names that contain
dots or apostrophes in the country name. That in
On 30.08.2011 13:38, Alexander Korotkov wrote:
On Tue, Aug 30, 2011 at 1:08 PM, Heikki Linnakangas<
heikki.linnakan...@enterprisedb.com> wrote:
Thanks. Meanwhile, I hacked together my own set of test scripts, and let
them run over the weekend. I'm still running tests with ordered data, but
he
On Thu, Sep 1, 2011 at 12:59 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> So I changed the test script to generate the table as:
>
> CREATE TABLE points AS SELECT random() as x, random() as y FROM
> generate_series(1, $NROWS);
>
> The unordered results are in:
>
>
On 01.09.2011 12:23, Alexander Korotkov wrote:
On Thu, Sep 1, 2011 at 12:59 PM, Heikki Linnakangas<
heikki.linnakan...@enterprisedb.com> wrote:
So I changed the test script to generate the table as:
CREATE TABLE points AS SELECT random() as x, random() as y FROM
generate_series(1, $NROWS);
T
2011/9/1 Dimitri Fontaine :
> Peter Eisentraut writes:
>> Well, we could make initdb patch it up, but that might seem excessive.
>
> I sometime wonder if archive_mode shouldn't default to "on" with the
> archive_command set to either '/bin/true' or 'rem' for windows.
>
> That allows to install pro
This is updates SP-GiST patch, which fixed one bug and
replaced test to the locale independent one.
On Wed, 31 Aug 2011, Oleg Bartunov wrote:
Hi there,
attached is our WIP-patch for 9.2 development source tree, which provides
implementation of SP-GiST (prototype was presented at PGCon-2011, s
Hi!
Ie expect some problems in support of comparison operators for text, because
locale string comparison can have unexpected behaviour.
Let's see the example. Create table with words and add extra leading space
to some of them.
test=# create table dict(id serial, word text);
NOTICE: CREATE TABL
On Fri, Aug 26, 2011 at 5:32 AM, Kohei KaiGai wrote:
> Yes. It also caches an expected security label when a client being
> labeled as "scontext" tries to execute a procedure being labeled as
> "tcontext", to reduce number of system call invocations on fmgr_hook
> and needs_fmgr_hook.
> If the exp
On Wed, Aug 31, 2011 at 9:45 AM, Gary Merkel wrote:
> Having trouble installing dblink under PostgreSQL 8.4.4 on MAC OS X 10.4.11
>
> Running make gives the following error:
>
> sed 's,MODULE_PATHNAME,$libdir/dblink,g' dblink.sql.in >dblink.sql
>
> gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototype
> On Fri, Aug 26, 2011 at 5:32 AM, Kohei KaiGai wrote:
> > Yes. It also caches an expected security label when a client being
> > labeled as "scontext" tries to execute a procedure being labeled as
> > "tcontext", to reduce number of system call invocations on fmgr_hook
> > and needs_fmgr_hook.
>
On Thu, Aug 18, 2011 at 6:19 PM, Josh Kupershmidt wrote:
> A few gripes about mb_regress.sh:
> 1. No exit code is specified, so even if there are differences
> between results/ and expected/ the script will still return 0.
>
> 2. The 'dropdb' command is used to wipe out the "utf8" database
> bef
Bruce Momjian wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Bruce Momjian writes:
> > > > It has been years since I ran src/tools/pginclude/pgrminclude to remove
> > > > unnecessary include files. (I have already fixed things so include
> > > > files can be compiled on their own.)
> > >
Excerpts from Bruce Momjian's message of jue sep 01 11:04:33 -0300 2011:
> Bruce Momjian wrote:
> > OK, try #2. I already had code that removed #if/#else/#endif code in
> > *.h files for better testing, so I extended that to all *.c files. This
> > reduces the size of the diff from 6.6k lines to
Alvaro Herrera writes:
> Excerpts from Bruce Momjian's message of jue sep 01 11:04:33 -0300 2011:
>> I have re-run the script and applied the result, again tested on BSD and
>> Linux. I will monitor the buildfarm for possible failures.
> I think anything of this sort should be tested on Windows
Alvaro Herrera wrote:
> Excerpts from Bruce Momjian's message of jue sep 01 11:04:33 -0300 2011:
> > Bruce Momjian wrote:
>
> > > OK, try #2. I already had code that removed #if/#else/#endif code in
> > > *.h files for better testing, so I extended that to all *.c files. This
> > > reduces the s
Tom Lane wrote:
> Alvaro Herrera writes:
> > Excerpts from Bruce Momjian's message of jue sep 01 11:04:33 -0300 2011:
> >> I have re-run the script and applied the result, again tested on BSD and
> >> Linux. I will monitor the buildfarm for possible failures.
>
> > I think anything of this sort
Hallow hackers
I have the following problem to solve and would like to get advice on
the best way to do it.
The problem:
When growing a pl/proxy based database cluster, one of the main
operations is splitting a partition. The standard flow is as follows:
1) make a copy of the partitions table(s
On Wed, Aug 31, 2011 at 8:13 AM, Bernd Helmle wrote:
> Out of curiosity,
>
> is anybody working on $subject? I'm currently planning to work on such a
> driver,
> but given the current stream of new drivers i want to make sure to not
> duplicate any efforts...
>
The most complete list I've seen of
On 8/31/11 12:15 PM, Merlin Moncure wrote:
> An out of process, autonomous transaction type implementation should
> probably not sit under stored procedures for a number of reasons --
> mainly that it's going to expose too many implementation details to
> the user. For example, does a SP heavy app
I wrote:
> What *does* seem feasible is to back-port just the single change we
> actually need, by copying the two relevant macros into one of our
> config/ source files for the configure script. I've tested that in
> 8.3 and it seems to work --- at least, the generated configure script
> changes
On Thu, Sep 1, 2011 at 1:18 PM, Josh Berkus wrote:
> On 8/31/11 12:15 PM, Merlin Moncure wrote:
>> An out of process, autonomous transaction type implementation should
>> probably not sit under stored procedures for a number of reasons --
>> mainly that it's going to expose too many implementation
> Seems like it would be better to fix archive_mode so that it can be
> changed without a restart.
+1
I'm also wondering if providing some shell script examples of a
fault-tolerant script to handle archiving would be useful.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
On Thu, Sep 1, 2011 at 3:05 PM, Josh Berkus wrote:
> +1
>
> I'm also wondering if providing some shell script examples of a
> fault-tolerant script to handle archiving would be useful.
I think it would.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Tom Lane wrote:
> Peter Eisentraut writes:
> > +# contrib/pg_upgrade/test.sh
> > +#
> > +# Test driver for pg_upgrade. Initializes a new database cluster,
> > +# runs the regression tests (to put in some data), runs pg_dumpall,
> > +# runs pg_upgrade, runs pg_dumpall again, compares the dumps.
>
Peter Eisentraut wrote:
> On tis, 2011-08-30 at 16:25 -0400, Tom Lane wrote:
> > So I think that as given, this script is only useful for testing
> > pg_upgrade of $currentversion to $currentversion. Which is surely
> > better than no test at all, but it would not for example have caught
> > the 8
On Wed, Aug 31, 2011 at 11:12 AM, Ross J. Reedstrom wrote:
> Hmm, this thread seems to have petered out without a conclusion. Just
> wanted to comment that there _are_ non-password storage uses for these
> digests: I use them in a context of storing large files in a bytea
> column, as a means to d
I've prepared a significantly simplified version of the patch. The two
main changes are
(a) it does not update the pg_stat_bgwriter anymore, it just prints an
info to the server log
(b) a new GUC is not required, it's driven by the log_checkpoints
This version will log at least 10 'checkpoint st
Tom Lane wrote:
> I wrote:
> > "Sergey E. Koposov" writes:
> >> I'm seeing something weird which looks like a bug in 9.1rc1 after the
> >> upgrade 8.4->9.0->9.1 done using pg_upgrade.
>
> > Hm, I wonder what pg_upgrade left relpages/reltuples set to ...
>
> Sure enough, that's the problem. pg_
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> It's off topic. But I think custom format would require a major mangling
> to be able to handle a complete cluster. This isn't just a simple matter
> of programming, IMNSHO.
Oh, I meant just having it create separate custom format files for
Hello everyone,
I am implementing some functionality into Postgresql, where I want to
track which row was accessed by a user query. I am implementing the
functionality inside Postgres, so that there are no changes required
on client side (e.g. re-writing queries).
Rows are identified by OIDs, and
Fazool writes:
> I am implementing some functionality into Postgresql, where I want to
> track which row was accessed by a user query. I am implementing the
> functionality inside Postgres, so that there are no changes required
> on client side (e.g. re-writing queries).
> Rows are identified by O
Thanks for the reply Tom.
As far as I know, the TID of a row can change over time (e.g. when the
row is updated). Isn't it so? If so, it wont solve my problem.
It says here (http://www.postgresql.org/docs/9.0/static/ddl-system-columns.html)
that
"The OID, or even better a user-defined serial numb
33 matches
Mail list logo
