Re: 7.0 RPMS and syslog problem. (more) - Mailing list pgsql-hackers

Upon further investigation, I found that when the hostname is broadcast to everyone, the following also appears in
/var/log/messages:

May 17 09:28:11 galaxy 
May 17 09:28:11 galaxy syslogd: Cannot glue message parts together
May 17 09:28:11 galaxy 135>May 17 09:28:11 postgres[18087]: query: SELECT c.relname as "Name", 'table'::text as "Type",
u.usenameas "Owner" FROM pg_class c, pg_user u WHERE c.relowner = u.usesysid AND c.relkind = 'r'   AND not exists
(select1 from pg_views where viewname = c.relname)   AND c.relname !~ '^pg_' UNION SELECT c.relname as "Name",
'table'::textas "Type", NULL as "Owner" FROM pg_class c WHERE c.relkind = 'r'   AND not exists (select 1 from pg_views
whereviewname = c.relname)   AND not exists (select 1 from pg_user where usesysid = c.relowner)   AND c.relname !~
'^pg_' UNION  SELECT c.relname as "Name", 'view'::text as "Type", u.usename as "Owner" FROM pg_class c, pg_user u WHERE
c.relowner= u.usesysid AND c.relkind = 'r'   AND exists (select 1 from pg_views where viewname = c.relname)   AND
c.relname!~ '^pg_' UNION SELECT c.relname as "Name", 'view'::text as "Type", NULL as "Owner" FROM pg_class c WHERE
c.relkind= 'r'   AND exists (select 1 from pg_views whe!
 
re viewname = c.relname)   AND not exists (select 1 fro
May 17 09:28:11 galaxy m pg_user where usesysid = c.relowner)   AND c.relname !~ '^pg_'  UNION  SELECT c.relname as
"Name",  (CASE WHEN relkind = 'S' THEN 'sequence'::text ELSE 'index'::text END) as "Type",   u.usename as "Owner" FROM
pg_classc, pg_user u WHERE c.relowner = u.usesysid AND relkind in ('S')   AND c.relname !~ '^pg_' UNION SELECT
c.relnameas "Name",   (CASE WHEN relkind = 'S' THEN 'sequence'::text ELSE 'index'::text END) as "Type",   NULL as
"Owner"FROM pg_class c WHERE not exists (select 1 from pg_user where usesysid = c.relowner) AND relkind in ('S')   AND
c.relname!~ '^pg_'  ORDER BY "Name"
 

So the problem seems to stem from the "Cannot glue message parts together"

The hostname is being broadcast to with the level of "emerg" because if I
remove:

*.emerg                                                        *

from my syslog.conf file, I dont see the console message getting broadcast
anymore.

If anyone else has seen this or has any ideas, please let me know :).

Mike