Thread: mailing list
Hi, this mailing list has lots of traffic (about 50 messages a day). Wouldn't it be more convenient to turn it into a news group? I have never seen a postgresQL news group on Usenet. It's really a hassle to move all messages in pgsql-general to a separate folder or to cut and paste when replying to a message within a digest. What do you think? Peter -- ------------------------------------------------------------------ Peter Maas, m+r infosysteme, D-52070 Aachen, Hubert-Wienen-Str. 24 Tel +49-241-875094 Fax +49-241-875095 eMail pm@mrinfo.de ------------------------------------------------------------------
Hi! I seem to be having a rather interesting problem. I'm using RH6.2, retrofitted with PGSQL 7.0.2. When I start postgres using pg_ctl, and add the option -o "-o -F" in order to disable fsync, everything still works - except that the database is inaccessible via network. Is there a workaround? postmaster.opts says that the option to listen on port 5432 is enabled, but when I telnet to port 5432, there is no service running. If I take out the -o "-o -F", it all starts working again. What is going wrong? Is this a bug? Or is network access disabled by default when no fsync is used? How do I enable network access with fsync disabled? Thanks. Gordan
* Peter Maas <pm@mrinfo.de> [001205 02:31] wrote: > Hi, > > this mailing list has lots of traffic (about 50 messages a day). > Wouldn't it be more convenient to turn it into a news group? I have > never seen a postgresQL news group on Usenet. It's really a hassle > to move all messages in pgsql-general to a separate folder or to > cut and paste when replying to a message within a digest. What do > you think? Er, there's a lot of utilities for managing mailing lists, procmail on UNIX and a boatload of clients for Windows have the ability to route mail based on email headers to seperate inboxes. Also, this has been brought up before and I'm pretty sure the concensus was that usenet attracts a lot of spam to its users. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk."
On Tue, 05 Dec 2000, Peter Maas wrote:
> Hi,
>
> this mailing list has lots of traffic (about 50 messages a day).
> Wouldn't it be more convenient to turn it into a news group? I have
> never seen a postgresQL news group on Usenet. It's really a hassle
> to move all messages in pgsql-general to a separate folder or to
> cut and paste when replying to a message within a digest. What do
> you think?
I just subscribed to this list with the command options:
subscribe
set digest
end
but this seems not to have worked as I'm getting the non-digestified
messages. Notice that this worked when subscribed to pgsql-sql
(although it didn't send a confirmation reply, just subscribed me).
I'd rather use old majordomo subscribe system.
Regards.
--
"California no longer exists, the dream is long dead ..."
- Mediterraneo -
* Alfred Perlstein <bright@wintelcom.net> [001205 05:18]: > * Peter Maas <pm@mrinfo.de> [001205 02:31] wrote: > > Hi, > > > > this mailing list has lots of traffic (about 50 messages a day). > > Wouldn't it be more convenient to turn it into a news group? I have > > never seen a postgresQL news group on Usenet. It's really a hassle > > to move all messages in pgsql-general to a separate folder or to > > cut and paste when replying to a message within a digest. What do > > you think? > > Er, there's a lot of utilities for managing mailing lists, procmail > on UNIX and a boatload of clients for Windows have the ability to > route mail based on email headers to seperate inboxes. > > Also, this has been brought up before and I'm pretty sure the > concensus was that usenet attracts a lot of spam to its users. > AND, there is already a NewsGroup: comp.databases.postgresql.general 0000010647 0000009863 y comp.databases.postgresql.hackers 0000003422 0000003423 y comp.databases.postgresql.admin 0000000741 0000000704 y comp.databases.postgresql.novice 0000000856 0000000818 y comp.databases.postgresql.committers 0000004057 0000003818 y comp.databases.postgresql.questions 0000000130 0000000130 y comp.databases.postgresql.docs 0000000211 0000000206 y comp.databases.postgresql.ports 0000000381 0000000369 y LER > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
In fact, there are even more then that: comp.databases.postgresql.admin 0000002519 0000002432 y comp.databases.postgresql.announce 0000000301 0000000301 y comp.databases.postgresql.bugs 0000001111 0000001110 y comp.databases.postgresql.docs 0000001187 0000001178 y comp.databases.postgresql.general 0000014613 0000013194 y comp.databases.postgresql.hackers 0000022503 0000022493 y comp.databases.postgresql.interfaces 0000004810 0000004810 y comp.databases.postgresql.patches 0000001454 0000001419 y comp.databases.postgresql.ports 0000002313 0000002268 y comp.databases.postgresql.questions 0000003657 0000003655 y comp.databases.postgresql.sql 0000004843 0000004663 y comp.databases.postgresql.committers 0000004750 0000004242 y comp.databases.postgresql.mirrors 0000000002 0000000002 y comp.databases.postgresql.novice 0000001072 0000000963 y comp.databases.postgresql.hackers.fmgr 0000000000 0000000001 y comp.databases.postgresql.hackers.oo 0000000017 0000000017 y comp.databases.postgresql.hackers.smgr 0000000000 0000000001 y comp.databases.postgresql.hackers.wal 0000000000 0000000001 y comp.databases.postgresql.interfaces.php 0000000112 0000000093 y and all the lists are gated between them local to the lists themselves, and I monitor them to make sure that they are still working ... ... *and* there has always been an open offer for any sites that want to feed directly from the source ... On Tue, 5 Dec 2000, Larry Rosenman wrote: > * Alfred Perlstein <bright@wintelcom.net> [001205 05:18]: > > * Peter Maas <pm@mrinfo.de> [001205 02:31] wrote: > > > Hi, > > > > > > this mailing list has lots of traffic (about 50 messages a day). > > > Wouldn't it be more convenient to turn it into a news group? I have > > > never seen a postgresQL news group on Usenet. It's really a hassle > > > to move all messages in pgsql-general to a separate folder or to > > > cut and paste when replying to a message within a digest. What do > > > you think? > > > > Er, there's a lot of utilities for managing mailing lists, procmail > > on UNIX and a boatload of clients for Windows have the ability to > > route mail based on email headers to seperate inboxes. > > > > Also, this has been brought up before and I'm pretty sure the > > concensus was that usenet attracts a lot of spam to its users. > > > AND, there is already a NewsGroup: > > comp.databases.postgresql.general 0000010647 0000009863 y > comp.databases.postgresql.hackers 0000003422 0000003423 y > comp.databases.postgresql.admin 0000000741 0000000704 y > comp.databases.postgresql.novice 0000000856 0000000818 y > comp.databases.postgresql.committers 0000004057 0000003818 y > comp.databases.postgresql.questions 0000000130 0000000130 y > comp.databases.postgresql.docs 0000000211 0000000206 y > comp.databases.postgresql.ports 0000000381 0000000369 y > > LER > > -- > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > "I have the heart of a child; I keep it in a jar on my desk." > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 972-414-9812 E-Mail: ler@lerctr.org > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Is there a news-server to connect to? My company has none, yet. /Roger -----Original Message----- From: The Hermit Hacker [mailto:scrappy@hub.org] Sent: den 5 december 2000 14:02 To: Larry Rosenman Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] mailing list In fact, there are even more then that: comp.databases.postgresql.admin 0000002519 0000002432 y comp.databases.postgresql.announce 0000000301 0000000301 y comp.databases.postgresql.bugs 0000001111 0000001110 y comp.databases.postgresql.docs 0000001187 0000001178 y comp.databases.postgresql.general 0000014613 0000013194 y comp.databases.postgresql.hackers 0000022503 0000022493 y comp.databases.postgresql.interfaces 0000004810 0000004810 y comp.databases.postgresql.patches 0000001454 0000001419 y comp.databases.postgresql.ports 0000002313 0000002268 y comp.databases.postgresql.questions 0000003657 0000003655 y comp.databases.postgresql.sql 0000004843 0000004663 y comp.databases.postgresql.committers 0000004750 0000004242 y comp.databases.postgresql.mirrors 0000000002 0000000002 y comp.databases.postgresql.novice 0000001072 0000000963 y comp.databases.postgresql.hackers.fmgr 0000000000 0000000001 y comp.databases.postgresql.hackers.oo 0000000017 0000000017 y comp.databases.postgresql.hackers.smgr 0000000000 0000000001 y comp.databases.postgresql.hackers.wal 0000000000 0000000001 y comp.databases.postgresql.interfaces.php 0000000112 0000000093 y and all the lists are gated between them local to the lists themselves, and I monitor them to make sure that they are still working ... ... *and* there has always been an open offer for any sites that want to feed directly from the source ... On Tue, 5 Dec 2000, Larry Rosenman wrote: > * Alfred Perlstein <bright@wintelcom.net> [001205 05:18]: > > * Peter Maas <pm@mrinfo.de> [001205 02:31] wrote: > > > Hi, > > > > > > this mailing list has lots of traffic (about 50 messages a day). > > > Wouldn't it be more convenient to turn it into a news group? I have > > > never seen a postgresQL news group on Usenet. It's really a hassle > > > to move all messages in pgsql-general to a separate folder or to > > > cut and paste when replying to a message within a digest. What do > > > you think? > > > > Er, there's a lot of utilities for managing mailing lists, procmail > > on UNIX and a boatload of clients for Windows have the ability to > > route mail based on email headers to seperate inboxes. > > > > Also, this has been brought up before and I'm pretty sure the > > concensus was that usenet attracts a lot of spam to its users. > > > AND, there is already a NewsGroup: > > comp.databases.postgresql.general 0000010647 0000009863 y > comp.databases.postgresql.hackers 0000003422 0000003423 y > comp.databases.postgresql.admin 0000000741 0000000704 y > comp.databases.postgresql.novice 0000000856 0000000818 y > comp.databases.postgresql.committers 0000004057 0000003818 y > comp.databases.postgresql.questions 0000000130 0000000130 y > comp.databases.postgresql.docs 0000000211 0000000206 y > comp.databases.postgresql.ports 0000000381 0000000369 y > > LER > > -- > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > "I have the heart of a child; I keep it in a jar on my desk." > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 972-414-9812 E-Mail: ler@lerctr.org > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
"Gordan Bobic" <gordan@freeuk.com> writes:
> I seem to be having a rather interesting problem. I'm using RH6.2,
> retrofitted with PGSQL 7.0.2. When I start postgres using pg_ctl, and add
> the option -o "-o -F" in order to disable fsync, everything still works -
> except that the database is inaccessible via network.
Sure sounds like you forgot to include -i in the postmaster's switches.
regards, tom lane
Hi, It is possible to upgrade the mailing list system to block of any unwanted attachment (e.g creative.exe, navidad.exe) ? Regards, Thomas
I'd like to get an idea of the overhead introduced by large quantity of
tables being hosted off a single PostgreSQL server. It is possible I'll be
wanting to host upwards of 200-500 tables per server. Essentially, will I
be surprised to find out that performance in PostgreSQL (or DBMS in
general) is significantly hindered by sheer quantity of tables? The tables
are small, with few rows and few columns. The queries are simple selects,
updates, inserts and deletes.
Appreciate any feedback on this, thanks.
- - - - - - -
- - - - -
WARNING: Some experts believe that use of any keyboard may cause serious
injury.
Consult Users Guide.
dfunct@telus.net
I would suggest something like what is in use at http://www.openacs.org . The advantage is that the posts are easier to archive / search / find. You still get delivery via email, but the disadvantage is that you cannot reply without going to the web page. Sam -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Peter Maas Sent: Tuesday, December 05, 2000 3:25 AM To: pgsql-general@postgresql.org Subject: [GENERAL] mailing list Hi, this mailing list has lots of traffic (about 50 messages a day). Wouldn't it be more convenient to turn it into a news group? I have never seen a postgresQL news group on Usenet. It's really a hassle to move all messages in pgsql-general to a separate folder or to cut and paste when replying to a message within a digest. What do you think? Peter -- ------------------------------------------------------------------ Peter Maas, m+r infosysteme, D-52070 Aachen, Hubert-Wienen-Str. 24 Tel +49-241-875094 Fax +49-241-875095 eMail pm@mrinfo.de ------------------------------------------------------------------
Soma Interesting <dfunct@telus.net> writes:
> I'd like to get an idea of the overhead introduced by large quantity of
> tables being hosted off a single PostgreSQL server. It is possible I'll be
> wanting to host upwards of 200-500 tables per server. Essentially, will I
> be surprised to find out that performance in PostgreSQL (or DBMS in
> general) is significantly hindered by sheer quantity of tables?
When you get to tens of thousands of tables per server, we might start
to worry a little... 500 is in the "what me worry?" class.
regards, tom lane