On Mon, Jun 9, 2008 at 10:17 PM, Tommy Cheng <[EMAIL PROTECTED]> wrote:
> you are right. I double checked. So, is there any way to turn off auto index
> creation for the parent? (the best is changing postgresql database setting)
> I am using postgres (PostgreSQL) 8.1.9 on CentOS 5 x86_64
>
Again,
On Tue, Jun 10, 2008 at 2:46 PM, Dinesh <[EMAIL PROTECTED]> wrote:
> Hi Scott,
>
> Thanks for your reply.
>
> Is there a built in exception in pl/pgsql ( similar to oracle's
> |DUP_VAL_ON_INDEX ) that I can use?
>
> I ran into an unique situation a couple of days ago. Procedure that inserts
> a new
On Wed, Mar 3, 2010 at 10:32, Dhimant Patel wrote:
> Hi All,
>
> I am working with latest source downloaded from postgres org site.
> I compiled and installed the source with --with-wal-segsize=2, assuming it
> should give me 4MB size xlog files. (As per the documentation it is a power
> of 2 valu
On Sun, Mar 28, 2010 at 16:27, Mike Williams wrote:
> Test are para-virt VMs with "regular" kernels, production are real
> machines with hardened kernels (grsec+pax).
Ive seen this error on a few boxes around here, using a non grsec
kernel fixes it. I never bothered to report it because I cant
r
On Tue, Mar 30, 2010 at 04:16, Mike Williams wrote:
> Thanks Alex, good to know I've not screwed up the kernel somehow.
>
> I've been using 2.6.32 with grsecurity-2.1.14-2.6.32.9-201002231820 applied.
Looks like the first instance I had of this problem was with
2.6.31.1-rc1-grsec. I know I tried
On Wed, May 19, 2010 at 16:25, ALEXANDER JOSE wrote:
> I have a question, I have postgres 8.2.5 on a windows server on another
> machine and I have suse linux enterprise 10 postgres 8.4, you perform a
> backup with pgadmin 1.10 to a database and restore the database in the
> version of postgres 8.
On Wed, May 19, 2010 at 06:30, Josi Perez (3T Systems)
wrote:
> To avoid to delete registers I created one trigger activated "before delete"
> with lines like that:
> UPDATE tableX set dtExc = 'now', userExc = current_user where idTableX =
> OLD.idTableX;
> return NULL;
>
> but, I need do the sam
On Sun, Jun 20, 2010 at 10:36, Elior Soliman wrote:
> Hello,
>
> My company looking for some solution for High availability with Postgres.
>
> Our optional solution is as follows :
> Two DB servers will be using a common external storage (with raid). Both
> servers are going to use the same DB fil
On Mon, Jul 26, 2010 at 16:01, Irene Barg wrote:
>> 2010-07-26 11:33:33 MST system_admin metadataERROR: could not write block
>> 503414 of temporary file: No space le
>> ft on device
>> 2010-07-26 11:33:33 MST system_admin metadataHINT: Perhaps out of disk
>> space?
>> -bash-3.2$ df -h
>> Files
On Tue, Jul 27, 2010 at 15:58, Irene Barg wrote:
> I'm afraid I don't understand how turning on 'log_temp_files' will help?
Well, postgres is probably doing exactly what its told. You just need
to figure out what that is and why. ( and if it is some kind of bug,
we wont be able to do anything ab
On Wed, Jul 28, 2010 at 15:43, Irene Barg wrote:
> Alex,
> The postmaster wouldn't start with shared_buffers = 5632MB, so we reduced it
> to 2GB. The system's shared memory is:
>
>> [dpp...@pipen18 ~]$ sudo /sbin/sysctl -a | grep kernel | grep shmmax
>> kernel.shmmax = 4182863872
You can bump tha
On Tue, Aug 24, 2010 at 07:36, Tom Lane wrote:
> I can see how "access to" might be read as specifically meaning "CONNECT
> privilege for". Should we change this message from "access to whatever"
> to "privileges for whatever", or some such wording?
+1, There have been a few times I found that m
2011/1/12 Achilleas Mantzios :
>
> Changed that to smth like: micros_total = micros_total + (double) micros;
> instead of the printf to beat any compiler optimization, and still linux runs
> at light speed:
> FBSD_TEST : user 0.089s, sys 1.4s
> FBSD_DEV : user 0.183s, sys 3.8s
> LINUX_PROD : user
On Thu, Feb 10, 2011 at 03:24, Sam Stearns wrote:
> Thanks, Norbert!
>
> I'll run the perl 5.10 upgrade past the guys.
>
> Sam
>
> On Thu, Feb 10, 2011 at 6:27 PM, Norbert Zacharias
> wrote:
perl -V
>>> Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
>>
>> May be an
On Fri, Jul 29, 2011 at 03:39, Rohan Kadam wrote:
> Hi All,
>
> I have currently upgraded our database from postgres 8.2 to 9.0. When trying
> to restore my old database dump taken form 8.2 version(using pg_dumpall), I
> observed that my timezone is getting changed and getting set to GMT instead
>
15 matches
Mail list logo
