Yeah, the things that matters are always on top of the changelog, so it's
not much trouble to look after then.
On Thu, Nov 7, 2013 at 9:00 PM, Adrian Klaver wrote:
> On 11/07/2013 11:07 AM, Greg Burek wrote:
>
>> On Wed, Nov 6, 2013 at 4:36 AM, Leonardo Carneiro
>> mailto:chesterma...@gmail.com>
On Mon, Nov 11, 2013 at 2:00 AM, Tomas Vondra wrote:
>
>> Would someone know the best way to get this to the right folks?
>>
>> Thanks in advance. (And sorry reporting to pgsql-general - the
>> developer list states emails must go elsewhere first).
>
> IMHO pgsql-hackers is the right audience for
G'day list.
I've recently upgraded a number of servers from PostgreSQL 9.2.5 to
9.3.1 and have started getting the following errors every couple of
hours along with some failed transactions. I have been unable to track
down any sort of rhyme or reason for the errors yet, so I figured I'd
check wit
On Tue, Nov 5, 2013 at 3:49 PM, sparikh wrote:
> Thanks Jeff for your quick response.
>
> I inherited this system and they had cron job which uses pg_dump for back
> up. I recently used to rsync to bring back my hot standby when it was out
> of
> sync and offline for few days because of space iss
Hello all,
I am creating a data model that contains time-dependent data. I only need a
snapshot solution, where we capture the initial state of all fields in the
record, and we then store subsequent changes as a new row in a child table.
What I am looking at is creating a primary table that contai
[moving the discussion to pgsql-hackers]
Jeffrey Walton wrote:
> The Analyzer is invoked with scan-build. Its used when compiling
> the package because it performs static analysis.
>
> The Santizers are invoked with the runtime flags. They are used
> with the `check` program because they perform
Melvin Call wrote
> Hello all,
>
> I am creating a data model that contains time-dependent data. I only need
> a
> snapshot solution, where we capture the initial state of all fields in the
> record, and we then store subsequent changes as a new row in a child
> table.
> What I am looking at is cr
On Mon, Nov 11, 2013 at 4:28 PM, David Johnston wrote:
> Melvin Call wrote
> > Hello all,
> >
> > I am creating a data model that contains time-dependent data. I only need
> > a
> > snapshot solution, where we capture the initial state of all fields in
> the
> > record, and we then store subseque
Good evening,
I could swear I read somewhere that the default integer size on 64-bit
systems running 9.1 is eight bytes, or the equivalent of a bigint. But
reading through the user guide it seems that it is indeed still just
four-bytes. Can anyone verify that for me, or point me to a way to verify
The following dropped out of `make check` for Postgres 9.3.1.
Any ideas how to clear the error? I could not locate answers when
searching the phrase.
Thanks in advance.
**
$ make check
...
mkdir ./testtablespace
../../../src/test/regress/pg_regress --inputdir=.
--temp-install=./tmp_che
On 11/11/2013 4:14 PM, Melvin Call wrote:
I could swear I read somewhere that the default integer size on 64-bit
systems running 9.1 is eight bytes, or the equivalent of a bigint. But
reading through the user guide it seems that it is indeed still just
four-bytes. Can anyone verify that for me,
On 11/11/2013 7:14 PM, Melvin Call wrote:
Good evening,
I could swear I read somewhere that the default integer size on 64-bit
systems running 9.1 is eight bytes, or the equivalent of a bigint. But
reading through the user guide it seems that it is indeed still just
four-bytes. Can anyone verify
On Mon, Nov 11, 2013 at 6:29 PM, John R Pierce wrote:
> On 11/11/2013 4:14 PM, Melvin Call wrote:
>
>> I could swear I read somewhere that the default integer size on 64-bit
>> systems running 9.1 is eight bytes, or the equivalent of a bigint. But
>> reading through the user guide it seems that i
On Mon, Nov 11, 2013 at 6:35 PM, Guy Rouillier wrote:
> On 11/11/2013 7:14 PM, Melvin Call wrote:
>
>> Good evening,
>>
>> I could swear I read somewhere that the default integer size on 64-bit
>> systems running 9.1 is eight bytes, or the equivalent of a bigint. But
>> reading through the user gu
Hi,
What are the real differences between the bgwriter and checkpointer
process? Both of them write data from the buffer to the data files, right?
Is it just a matter of 'when' they write?
Regards,
Jayadevan
Jeffrey Walton writes:
> The following dropped out of `make check` for Postgres 9.3.1.
Sure you've got a complete source tree? There ought to be files in
that directory:
$ ls src/test/regress/input
constraints.sourcecreate_function_2.source security_label.source
copy.source
Hi everyone,
I have few question about checkpoints during create database.
First just extract from log on my test database 9.2.4:
2013-11-12 03:48:31 MSK 1717 @ from [vxid: txid:0] [] LOG: checkpoint
starting: immediate force wait
2013-11-12 03:48:31 MSK 1717 @ from [vxid: txid:0] [] LOG: ch
Postgres 8.4 on OEL 6.3 Linux is having issues that the DBs are not available
at intervals. I bumped up the debug level to 4 and all I see in the
/var/lib/pgsql/data/pg_log are logs that say..
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the d
On Mon, Nov 11, 2013 at 6:32 PM, Shree wrote:
> Also pg_ctl command to stop, restart does not seem to have any effect.
> Does anyone have any ideas?
>
I can't speak to what issued the shutdown command, but have you tried
"pg_ctl restart -m fast" to expedite the restart (if that is indeed what
y
Thanks Tom.
On Mon, Nov 11, 2013 at 8:51 PM, Tom Lane wrote:
> Jeffrey Walton writes:
>> The following dropped out of `make check` for Postgres 9.3.1.
>
> Sure you've got a complete source tree? There ought to be files in
> that directory:
>
> $ ls src/test/regress/input
> constraints.source
Jeffrey Walton writes:
> From below, I'm thinking --inputdir might not be quite correct. `mkdir
> ./testtablespace` creates testtablespace in regress/, not input/. I'd
> like to try --inputdir=./input/.
> The GNUmakefile in the top level directory and the regress/ directory
> do not include the st
On Tue, Nov 5, 2013 at 11:35 AM, Christian Ullrich wrote:
> Hence my suspicion that it doesn't. I did not have the time to compare every
> function call yet.
It doesn't. But it's a pretty close match; it looks like it was ported
directly from the libpq code. libpq actually uses the same code path
On Mon, Nov 11, 2013 at 10:51 PM, Brian Crowell wrote:
> I think I'm getting closer though. I have psql on Windows successfully
> authenticating, so I can't be too far off.
Got it.
The NpgsqlPasswordPacket class has a bug: a utility function it calls
appends a null character to the data, which c
On 12 November 2013 07:49 Maxim Boguk wrote:
>Hi everyone,
>
>I have few question about checkpoints during create database.
>
>First just extract from log on my test database 9.2.4:
>
>2013-11-12 03:48:31 MSK 1717 @ from [vxid: txid:0] [] LOG: checkpoint
>starting: immediate force wait
>2013-11-
* From: Brian Crowell
> On Mon, Nov 11, 2013 at 10:51 PM, Brian Crowell wrote:
> > I think I'm getting closer though. I have psql on Windows successfully
> > authenticating, so I can't be too far off.
>
> Got it.
Great!
> The NpgsqlPasswordPacket class has a bug: a utility function it calls
>
On Mon, Nov 11, 2013 at 10:26 PM, Tom Lane wrote:
> Jeffrey Walton writes:
>> From below, I'm thinking --inputdir might not be quite correct. `mkdir
>> ./testtablespace` creates testtablespace in regress/, not input/. I'd
>> like to try --inputdir=./input/.
>> The GNUmakefile in the top level dir
26 matches
Mail list logo
