Re: [HACKERS] IDE

2007-10-01 Thread Adrian Maier
On 10/1/07, Pedro Belmino [EMAIL PROTECTED] wrote:
 Hello,
 I am having problems of productivity with IDE that I am using. Exists some
 IDE that recommended to develop postgresql?

Hello Pedro,

You are probably looking for a tool like pgAdmin (http://www.pgadmin.org) or
PhpPgAdmin (http://phppgadmin.sourceforge.net).   There are also some
commercial applications : http://www.postgresql.org/download/commercial

However,  please take notice that your question is not suited for the
pgsql-hackers mailing list : this list is for discussions about developing
PostgreSQL itself.


Cheers,
Adrian Maier

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] IDE

2007-10-01 Thread Michael Glaesemann


On Oct 1, 2007, at 10:27 , Adrian Maier wrote:


On 10/1/07, Pedro Belmino [EMAIL PROTECTED] wrote:

Hello,
I am having problems of productivity with IDE that I am using.  
Exists some

IDE that recommended to develop postgresql?


Hello Pedro,

You are probably looking for a tool like pgAdmin (http:// 
www.pgadmin.org) or

PhpPgAdmin (http://phppgadmin.sourceforge.net).   There are also some
commercial applications : http://www.postgresql.org/download/ 
commercial


However,  please take notice that your question is not suited for the
pgsql-hackers mailing list : this list is for discussions about  
developing

PostgreSQL itself.


That may be what he means. Unfortunately develop PostgreSQL can be  
taken both ways.


In case he's working on internals, I believe Emacs is used by a  
number of PostgreSQL hackers. And as for developing PostgreSQL-backed  
applications, I find $EDITOR + psql to work quite well.


Michael Glaesemann
grzm seespotcode net



---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] IDE

2007-10-01 Thread Dimitri Fontaine
Le lundi 01 octobre 2007, Michael Glaesemann a écrit :
 That may be what he means. Unfortunately develop PostgreSQL can be
 taken both ways.

 In case he's working on internals, I believe Emacs is used by a
 number of PostgreSQL hackers. And as for developing PostgreSQL-backed
 applications, I find $EDITOR + psql to work quite well.

In this case the slides from Neil  Gavin presentation about PostgreSQL 
hacking may be a good starting read:
  http://neilconway.org/talks/hacking/

IIRC, they also mention cscope (there's a user friendly kscope GUI of it) to 
easily browse code structures and call graphs.
  http://cscope.sourceforge.net/
  http://kscope.sourceforge.net/

Hope this helps, regards,
-- 
dim


signature.asc
Description: This is a digitally signed message part.


Re: [HACKERS] IDE

2007-10-01 Thread Adrian Maier
On 10/1/07, Michael Glaesemann [EMAIL PROTECTED] wrote:

  Hello Pedro,
 
  You are probably looking for a tool like pgAdmin (http://
  www.pgadmin.org) or
  PhpPgAdmin (http://phppgadmin.sourceforge.net).   There are also some
  commercial applications : http://www.postgresql.org/download/
  commercial
 
  However,  please take notice that your question is not suited for the
  pgsql-hackers mailing list : this list is for discussions about
  developing
  PostgreSQL itself.

 That may be what he means. Unfortunately develop PostgreSQL can be
 taken both ways.

 In case he's working on internals, I believe Emacs is used by a
 number of PostgreSQL hackers. And as for developing PostgreSQL-backed
 applications, I find $EDITOR + psql to work quite well.

Oh, you are right Michael.  I've missed the second interpretation of Pedro's
words.  My apologises if I got it wrong ...

-- 
Adrian Maier

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [HACKERS] IDE

2007-10-01 Thread Chuck McDevitt
If you are talking about working on the code (internals), I find eclipse
works very well for working on PostgreSQL.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pedro Belmino
Sent: Monday, October 01, 2007 6:42 AM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] IDE

 

Hello,
I am having problems of productivity with IDE that I am using. Exists
some IDE that recommended to develop postgresql?

I am thankful,

-- 
Pedro Belmino.



Re: [HACKERS] IDE Drives and fsync

2003-10-13 Thread Tom Lane
scott.marlowe [EMAIL PROTECTED] writes:
 Tom, you had mentioned adding a delay of some kind to the fsync logic, and 
 I'd be more than willing to try out any patch you'd like to toss out to me 
 to see if we can get a semi-stable behaviour out of IDE drives with the 
 -W1 and -f switches turned on.

I'd suggest experimenting with the delay in mdsync() in
src/backend/storage/smgr/md.c.  A larger delay should theoretically make
things more reliable.

If you see signs of corruption of the WAL itself, another knob you could
fool with is the wal_sync_method setting in postgresql.conf.  I have no
idea whether different sync methods would improve the odds of getting
the drive to write WAL sectors in the right order, but it'd be worth
experimenting with.

I dunno whether you have the ability to experiment with a dual-drive
machine, but it would certainly be worth revisiting all these tests
on a setup with WAL on a separate drive.

regards, tom lane

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org


Re: [HACKERS] IDE Drives and fsync

2003-10-08 Thread Manfred Spraul
scott.marlowe wrote:

OK, I've done some more testing on our IDE drive machine.

First, some background.  The hard drives we're using are Seagate 
drives, model number ST380023A.  Firmware version is 3.33.  The machine 
they are in is running RH9.  The setup string I'm feeding them on startup 
right now is:  hdparm -c3 -f -W1 /dev/hdx

where:

-c3 sets I/O to 32 bit w/sync (uh huh, sure...)

sync has nothing to do with sync to disk. The sync means read from three 
magic io ports before transfering data to or from the device.


-f sets the drive to flush buffer cache on exit

-f shouldn't have any effect: it means that the buffer cache in the OS 
is flushed after hdparm exits, it has no long-term effect on the disk.

-W1 turns on write caching

That's the problem: turning on write caching causes corruptions.
What's needed is partial write caching: write cache on, and fsync() 
sends a barrier to the disk, and only after the disk reports that the 
barrier is completed, then fsync() returns.
I consider that an OS/driver problem, not a problem for postgres.

The drives come up using DMA.  turning unmask IRQ on / off has no affect 
on the tests I've been performaing.
 

Of course. irq unmasking is about interrupt latency if DMA is not used: 
DMA off and dma masking off results in dropped bytes on serial links.

Without the -f switch, data corruption due to sudden power down is an 
almost certain.

It's odd that adding -f reduces the corruptions - probably it changes 
available memory, and thus the writeback of data from kernel to disk.

Tom, you had mentioned adding a delay of some kind to the fsync logic, and 
I'd be more than willing to try out any patch you'd like to toss out to me 
to see if we can get a semi-stable behaviour out of IDE drives with the 
-W1 and -f switches turned on.

I'm not aware that there is any safe delay. Disks with write caches 
reorder io operations, and some hold back write operations indefinitively.

Unfortunately Linux doesn't implement write barriers, and the support in 
some IDE disks is missing, too :-(

--
   Manfred
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
 joining column's datatypes do not match