Re: [GENERAL] Introduction
On 30 May 2013 14:48, Chris Angelico ros...@gmail.com wrote: On Thu, May 30, 2013 at 6:02 AM, Corbett, James james.corb...@cra-arc.gc.ca wrote: For those twenty years as a developer I should say that I have been completely blind, relying upon a screen review application known as JAWS and a Braille display. I’m looking forward to being part of this list. Welcome! One thing I'm very happy with in today's world, as improved on (say) two decades ago, is the way that computers have become accessible to more people; back in the 90s, I was playing with some of the speech navigation / speech synthesis tools that were available then, and they seemed more like toys than anything truly usable. Sure, you could get around without seeing the screen, but it was a struggle. Today, legally or completely blind people can even play text roleplaying games, thanks to years of smart development work. You're now using what is, in my opinion, the best database engine in the world. And it's language-agnostic, so you can happily use Java for some things, Python for others, Pike if you've ever heard of it, and even PHP if you're sadistic enough. I love it. Can I just say that I love being on this list. In the past I have asked some pretty daft questions, but the responses here have always been patient and helpful. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Insufficient privileges.
I am getting the following error message in my Drupal install. PDOException: SQLSTATE[42501]: Insufficient privilege: 7 ERROR: permission denied for sequence currenttest_id_seq: INSERT INTO currentTest (score) VALUES (:db_insert_placeholder_0); This is a table that I created using the postgres super user. I have tried to grant the drupal user (drupaluser) privileges to the table with: GRANT ALL ON currentTest to drupaluser; but this fails to resolve the issue. Can anyone suggest a way forward? Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Insufficient privileges.
Hi Rick, Thanks for the response. What is the sequence? and how do I grant the privileges needed to insert data into the database? Is it a postgres issue? ~ Dave On 7 July 2011 19:05, Rick Genter rick.gen...@gmail.com wrote: On Thu, Jul 7, 2011 at 10:03 AM, Dave Coventry dgcoven...@gmail.com wrote: I am getting the following error message in my Drupal install. PDOException: SQLSTATE[42501]: Insufficient privilege: 7 ERROR: permission denied for sequence currenttest_id_seq: INSERT INTO currentTest (score) VALUES (:db_insert_placeholder_0); This is a table that I created using the postgres super user. I have tried to grant the drupal user (drupaluser) privileges to the table with: GRANT ALL ON currentTest to drupaluser; but this fails to resolve the issue. Can anyone suggest a way forward? From the message I'd say that the drupal user doesn't have access to the sequence, which is a separate object from the table. -- Rick Genter rick.gen...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Insufficient privileges.
Hi John, Thanks. On 7 July 2011 21:48, John R Pierce pie...@hogranch.com wrote: I recommend dropping your drupal database (since I doubt its worked right if the objects are owned by postgres), and recreate it owned by the drupaluser, then let the drupaluser populate it during the initial install. :~) Well that's a little drastic at this stage! In actual fact the database drupaldb is owned by the drupaluser, so it's not really necessary. or, if I'm misreading your problem, and drupal itself is running but this is an extra non-drupal table you manually created, then ALTER TABLE OWNER drupaluser; Yes, that's what I was trying to do. Using the Drupal Nodes seems awfully cumbersome for what I'm trying to achieve so I added a sort of scratch table that I was hoping to manipulate. I have gone back to using the prescribed Drupal method as time was starting to run out and I needed a working prototype. I do intend to return to using the scratch table after the rush is over and I'll give your suggestion a try: it looks as though it may very well do the trick. drupal doesn't really interface very well to non-drupal data... the drupal approach is to define a new content type with the fields you need, then populate it via create content, choosing that new type, or use the various drupal APIs from your custom PHP modules. Yes, I'm finding that out. Thanks very much for your input. Regards, Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Postgres errors in Drupal install.
I'm having huge problems with a Drupal install using Postgres 8.4.8. I'm getting the following error: PDOException: SQLSTATE[08006] [7] could not connect to server: Connection refused Is the server running on host localhost and accepting TCP/IP connections on port 5432? in lock_may_be_available() (line 164 of /var/www/includes/lock.inc). The Site is under minimal load with possibly two or three people on it at once. Can anyone tell me why I get the error every hour or so? And what steps I could take to remedy this? Many thanks, Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Postgres errors in Drupal install.
Thank you very much for your responses.
On 26 June 2011 21:54, Peter Bex peter@xs4all.nl wrote:
Do you get the error in the logs or do you see it while going to the
site manually and does it show this instead of rendering a page?
The log don't really give much indication of anything untoward
happening. It's really that the page stops rendering and displays the
message.
If it's in the logs, and you're running cron or poorman's cron once
an hour, it could be that's where these messages are coming from.
You can run cron manually from the interface somewhere, so you
can try if you can reproduce the error more reliably and work from
there.
It doesn't seem quite regular enough to be part of the cron job.
Having said that the errors below do make reference to cron.
--- snip
--
2011-06-26 15:57:15 EDT STATEMENT: SELECT base.fid AS fid, base.uid
AS uid, base.filename AS filename, base.uri AS uri, base.filemime AS
filemime, base.filesize AS filesize, base.status AS status,
base.timestamp AS timestamp
FROM
file_managed base
WHERE (base.fid IN ('0', 'Upload', 'Remove', ''))
2011-06-26 15:57:15 EDT WARNING: nonstandard use of \\ in a string
literal at character 185
2011-06-26 15:57:15 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:30 EDT WARNING: nonstandard use of \\ in a string
literal at character 115
2011-06-26 15:57:30 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:31 EDT WARNING: nonstandard use of \\ in a string
literal at character 256
2011-06-26 15:57:31 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:31 EDT WARNING: nonstandard use of \\ in a string
literal at character 248
2011-06-26 15:57:31 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:31 EDT WARNING: nonstandard use of \\ in a string
literal at character 256
2011-06-26 15:57:31 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:31 EDT WARNING: nonstandard use of \\ in a string
literal at character 248
2011-06-26 15:57:31 EDT HINT: Use the escape string syntax for
backslashes, e.g., E'\\'.
2011-06-26 15:57:31 EDT ERROR: duplicate key value violates unique
constraint semaphore_pkey
2011-06-26 15:57:31 EDT STATEMENT: INSERT INTO semaphore (name,
value, expire) VALUES ('cron', '2399653214e078f2b5a48e5.75113719',
'1309118491.3697')
--- snip
--
Here are the messages in the logs of the last crash which might throw
a bit of light onto the subject for anyone rather more knowledgeable
than I:
--- snip
--
2011-06-26 17:13:24 EDT LOG: background writer process (PID 505) was
terminated by signal 9: Killed
2011-06-26 17:13:24 EDT LOG: terminating any other active server processes
2011-06-26 17:13:24 EDT WARNING: terminating connection because of
crash of another server process
2011-06-26 17:13:24 EDT DETAIL: The postmaster has commanded this
server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared
memory.
2011-06-26 17:13:24 EDT HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2011-06-26 17:13:24 EDT LOG: all server processes terminated; reinitializing
2011-06-26 17:13:24 EDT FATAL: could not create shared memory
segment: Cannot allocate memory
2011-06-26 17:13:24 EDT DETAIL: Failed system call was
shmget(key=5432001, size=29278208, 03600).
2011-06-26 17:13:24 EDT HINT: This error usually means that
PostgreSQL's request for a shared memory segment exceeded available
memory or swap space. To reduce the request size (currently 29278208
bytes), reduce PostgreSQL's shared_buffers parameter (currently 3072)
and/or its max_connections parameter (currently 103).
The PostgreSQL documentation contains more information about shared
memory configuration.
--- snip
--
While the server is a little challenged in the way of RAM, it is by no
means under any sort of load.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Postgres errors in Drupal install.
Apologies, I didn't notice that I was replying off-list. On 27 June 2011 00:29, Dave Coventry dgcoven...@gmail.com wrote: On 26 June 2011 23:37, John R Pierce pie...@hogranch.com wrote: I didn't read the whole thread, but is this a Linux server? Linux has a horrible feature, the Out of Memory Killer, which kills off processes when the system is low on memory. the OOM-Killer usually leaves log entries in DMESG and maybe /var/log/messages Yes, it's a Ubuntu 10.10 server. I don't actually see anything in dmesg or in /var/log/messages that would indicate indiscriminate culling of processes. If in fact its the OOM killer, you should probably lower your WORK_MEM and SHARED_BUFFERS and maybe MAINTENANCE_WORK_MEM in postgresql.conf Thanks for the suggestions. I have pulled them all down to their recommended minimums: work_mem: 64kB shared_buffers: 128kB maintenance_work_mem: 1MB I'll see if that makes any difference. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Oracle / PostgreSQL comparison...
I would just like to add my voice to those praising the community support provided by this list. I am not a DBA, and merely tinker with a few databases, mostly on the web. As such, my questions have occasionally bordered on the very silly, but I have always had them answered courteously, helpfully and with a great deal of patience, in stark contrast to MySQL lists which tend to veer towards the sarcastic, the minimal and the obscure. Kind Regards, Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Cognitive dissonance
My tupp'th: Formatted text, whether PDF, HTML or (heaven forbid!) Word Documents, is easier to read than unformatted plain text, and those of us without the OP's very admirable proficiency in vi remain at the mercy of the various readers and their associated search functions. However, I sure that it's not too arduous a task to extract the text in these documents and strip them of their formatting? Or am I missing something? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] export data to excel
There is also the Java POI classes (Poor Obfuscation Implementation) for importing and exporting doc and docx, HSSF (Horrible SpreadSheet Format) for exporting and importing xls and xlsx, http://poi.apache.org/ There are also implementations for Outlook, Powerpoint and Visio. Java can be integrated with PostgreSQL using the JDBC drivers: http://jdbc.postgresql.org/ Hope this helps. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] FOSDEM dinner
Sounds great fun! However, I presume I'm on the wrong Continent! ;) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] FOSDEM dinner
Yes, I'm in South Africa, which might make it problematic! 2010/1/14 Dave Page dp...@pgadmin.org: On Thu, Jan 14, 2010 at 1:14 PM, Dave Coventry dgcoven...@gmail.com wrote: Sounds great fun! However, I presume I'm on the wrong Continent! ;) I have no idea. I'm on the wrong landmass though, so there will be at least one person arriving by air :-) -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Java Postgres drivers.
I'm not sure this is the right place to enquire...
I'm trying to connect to a postgres datanbase with Java.
import java.sql.*;
public static void main(String[] args) {
// TODO code application logic here
try{
System.out.println(Starting...);
Class.forName(org.postgresql.Driver);
String url=jdbc:postgresql:inenergy;
System.out.println(Got here...);
catch(Exception e){
System.out.println(Error...+e.getMessage());
}
}
Just don't get to the 'Got here...' statement.
Can anyone see what I'm doing wrong?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Books, the lulu.com scam
2009/11/21 Yordan Radunchev jordan.radunc...@gmail.com: Postgre have such a great (and helpful and wiling to share knowledge) community and great on-line documentation for free. +1 Books (content) tent to get old and more useless with every Postgre update. If some one offers a book with lifetime support meaning that it will be updated regularly following Postgre updates - that will be an offer... but still - I don't need a book. I bought an O'Rielly Javascript book once, but had to ask a question online on the javascript group. I was flamed for using outdated documentation. (And they never even answered my question, either) This Postgres list is one of the most helpful around; thank you all! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] column does not exist error
Tearing my hair out, can anyone see what I'm doing wrong? SELECT title FROM node WHERE type=client; ERROR: column client does not exist LINE 1: SELECT title FROM node WHERE type=client; Yet this works: SELECT type FROM node; type client client client client client (5 rows) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Out of sync Primary Key Index
I have deleted a record from a table and am now getting errors:
INSERT INTO content_node_field (field_name, type, global_settings,
required, multiple, db_storage, module, db_columns, active, locked)
VALUES ('field_client_name', 'text',
'a:4:{s:15:text_processing;s:0:;s:10:max_length;s:0:;s:14:allowed_values;s:0:;s:18:allowed_values_php;s:0:;}',
0, 0, 1, 'text',
'a:1:{s:5:value;a:5:{s:4:type;s:4:text;s:4:size;s:3:big;s:8:not
null;b:0;s:8:sortable;b:1;s:5:views;b:1;}}', 1, 0);
ERROR: duplicate key value violates unique constraint content_node_field_pkey
My table is as follows:
\d content_node_field;
Table public.content_node_field
Column | Type | Modifiers
-++
field_name | character varying(32) | not null default
''::character varying
type| character varying(127) | not null default
''::character varying
global_settings | text | not null
required| smallint | not null default 0
multiple| smallint | not null default 0
db_storage | smallint | not null default 1
module | character varying(127) | not null default
''::character varying
db_columns | text | not null
active | smallint | not null default 0
locked | smallint | not null default 0
Indexes:
content_node_field_pkey PRIMARY KEY, btree (field_name)
From googling I need to reset my Primary Key, but
reindex index content_node_field_pkey;
REINDEX
Doesn't make any difference (no error is returned)
Nor does
reindex table content_node_field;
REINDEX
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] postgresql on windows98
I've got Postgres running on colinux which works well under windows XP, not sure how it will do under windows '98. (Not very well, according to this: http://colinux.wikia.com/wiki/FAQ#Q11._Is_it_possible_to_run_coLinux_under_98.2FME.3F ) 2009/5/14 Richard Huxton d...@archonet.com: Well, the perhaps more generous answer is try cygwin - there's a PostgreSQL package for it and it appears to be 8.2.9 (which isn't too old although see if there's the latest 8.2 available). However, assuming anyone running Windows 98 is doing so on hardware from 2000 or earlier, you've probably got at best 256MB of RAM and an aging disk too. It's going to be slow, and when the hardware goes wrong you're probably going to get database corruption. You might well get it when Windows crashes too. If you do get things running, you'll want to tune the database quite carefully to avoid bringing the system to a halt with one big query. You'll also want to ensure backups are taken on a regular basis. -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Annoying Reply-To
2008/10/23 Steve Atkins [EMAIL PROTECTED]: If you don't like it (and this applies to everyone else arguing about it, on either side) please do one of these three things: 1. Fix it locally at your end, as is trivial to do with procmail, amongst other approaches, and quit whining about it. or 2. Quit whining about it. or 3. Find somewhere else to whine about it and quit whining about it here. Cheers, Steve On Fri, 17 Oct 2008, Bill Moran wrote: You can resent it or not, but this _is_ a personal thing. It's personal because you are the only one complaining about it. Despite the large number of people on this list, I don't see anyone jumping in to defend you. Personally I am of the view that, as I am on this list principally to get support from it, and I am quite prepared to submit to the vagaries and oddities of the list behaviour in pursuit of the answers I might seek. As such, I am quite prepared to 1) Fix it my end, 2) Quit whining about it and 3) Find something else to whine about. However, the point is made by Bill that 'only one person' might feel that the reply-to configuration could be improved, and I feel compelled to say that, while I might not be driven to complain about the list behaviour myself, I do feel that the OP does have a point. And that's all that I'm going to say on the matter. - Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Annoying Reply-To
I am a member of a number of lists, some of which exhibit this 'reply-to' behaviour and I have also managed to adapt... to a point. Sometimes, however, I do end up replying directly to the poster rather than through the list. Tellingly, I very nearly sent this post directly to Serge Fonvilee. Without wanting to be too controversial, I have generally found that the lists which have the default reply configured like this do tend to be those that are dominated by members who are, shall we say, pedantic about protocol and 'netiquette'. Personally I would prefer the default reply-to to go to the list, but I'm not really bothered about it. My 2 cents. Disclaimer: If we are not talking about the default 'reply-to' behaviour of this list, please ignore this post; I came upon the thread late and it is possible that I am at cross purposes. Kind reagards, Dave Coventry 2008/10/17 Serge Fonville [EMAIL PROTECTED]: Altough I am not sure what the real issue is, I do know that on (for example) the tomcat mailing list, when I choose reply (in gmail) the to: field contains the address of the mailing list. Based on what I know, this should be relatively easy to set up in the mailing list manager. just my 2ct Serge Fonvilee -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] SAST FATAL: could not access private key file server.key
On Wed, Jul 2, 2008 at 5:13 PM, Albe Laurenz [EMAIL PROTECTED] wrote: If you don't care, you could 1) remove the symbolic link. 2) copy the key file to server.key in the PostgreSQL directory. 3) chown the copy of the file. Okay, I'll do that. Do you need SSL support at all? If not, just disable it and all your troubles are gone. Well, not at the moment, I'll try that as a last resort. If it worked before, then somebody must have changed something in the meantime. Since it must have been root, you should be able to track down who or what it was. Well, I'm the only person who was using it as root, so it must've been something I've done, dammit! Many people posted the link to the documentation. Read and enjoy! Yes, I've had a look at it, and have tried to follow instructions therein, but I'm not sure I understand it. PS: It is better to CC the list. Oh, sorry! I'm a member of several lists, and some default the reply to the list and some to the poster; I keep forgetting which is which! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] SAST FATAL: could not access private key file server.key
On Tue, Jul 1, 2008 at 5:52 PM, Albe Laurenz [EMAIL PROTECTED] wrote: If you don't need SSL, set 'ssl=off' in postgresql.conf. If you want SSL, 1) read the manual on SSL support http://www.postgresql.org/docs/8.3/static/ssl-tcp.html 2) Is there a file server.key? If yes, make it readable to the postgres user. If not, create it as documented. Hi Albe, thanks very much for helping me here... Here is the contents of my /var/lib/postgresql/8.2/main/ : [EMAIL PROTECTED]:/var/lib/postgresql/8.2/main# ls -l total 9 drwx-- 7 postgres postgres 168 2008-06-29 11:27 base drwx-- 2 postgres postgres 768 2008-06-30 13:01 global drwx-- 2 postgres postgres 72 2008-06-24 09:37 pg_clog drwx-- 4 postgres postgres 96 2008-06-24 09:37 pg_multixact drwx-- 2 postgres postgres 72 2008-06-24 09:37 pg_subtrans drwx-- 2 postgres postgres 48 2008-06-24 09:37 pg_tblspc drwx-- 2 postgres postgres 48 2008-06-24 09:37 pg_twophase -rw--- 1 postgres postgres 4 2008-06-24 09:37 PG_VERSION drwx-- 3 postgres postgres 120 2008-06-24 09:37 pg_xlog -rw--- 1 postgres postgres 125 2008-06-30 08:59 postmaster.opts lrwxrwxrwx 1 root root 31 2008-06-24 09:37 root.crt - /etc/postgresql-common/root.crt lrwxrwxrwx 1 root root 36 2008-06-24 09:37 server.crt - /etc/ssl/certs/ssl-cert-snakeoil.pem lrwxrwxrwx 1 root root 38 2008-06-24 09:37 server.key - /etc/ssl/private/ssl-cert-snakeoil.key 'server.key' seems to be writable to all and sundry, although the file it is linked to (ssl-cert-snakeoil.key) is not: [EMAIL PROTECTED]:/etc/ssl/private# ls -l total 4 -rw--- 1 root ssl-cert 887 2008-06-11 12:18 ssl-cert-snakeoil.key -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] SAST FATAL: could not access private key file server.key
When starting Postgres I get the following: [EMAIL PROTECTED]:/home/it# /etc/init.d/postgresql-8.2 start * Starting PostgreSQL 8.2 database server * The PostgreSQL server failed to start. Please check the log output: 2008-07-01 13:37:39 SAST FATAL: could not access private key file server.key: Permission denied What is the server key? And how do I make it accessible? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Controlling write access to a table
Hi. I have a database with all of the particulars of our students and I am adding a table that will contain all of the courses and the grades attained by the students. All this information is to be read by just about everybody, and the bulk of the data will be written by several clerks, and, while we wouldn't like just anybody altering these, we don't need terribly stringent write security. The marks (or grades) of the students are a different matter and we want to restrict changes to this data to a very few people. I'm presuming that this is not a unique problem, but I have been unable to find anything helpful on google. Can anyone assist me? Would it be preferable to create a separate database for this information? Regards, Dave Coventry -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Controlling write access to a table
On Wed, Jun 18, 2008 at 1:11 PM, David [EMAIL PROTECTED] wrote: Hi Dave. Did you intentionally mail me off-list? On-list is generally better so other people can give suggestions. No, sorry. I've just joined the list and am a little unused to it's mechanics. I appreciate that any solution offered (and any debate thereon) is important and adds to the knowledgebase. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
