Triggers not being fired with pglogical
2016-05-31 15:44:13 GMT
I have a feeling that slight enhancement to commands "SET ROLE" or "SET SESSION AUTHORIZATION" can obsolete and outperform external connection pooling tools in some use cases. Assume we are in the following situation: - There are a million schemas each owned by a distinct role. - Every role is not allowed to access any other schema except its own. If command "SET SESSION AUTHORIZATION" is enhanced to accept two additional arguments PASSWORD <password> , then a client simply establishes only one connection to server and do jobs for a million roles. Say I want to gain full access to "schema2", I simply issue these two commands SET SESSION AUTHORIZATION user2 PASSWORD p2; SET SEARCH_PATH TO schema2,pg_category; , where "p2" is the password associated with role "user2". If the current role is superuser "postgres" and it wants to downgrade itself to role "user3", then it simply sends these commands: SET SESSION AUTHORIZATION user3; SET SEARCH_PATH TO schema3,pg_category; Does my points make sense? Is it eligible for feature request? Best Regards, CN -- http://www.fastmail.com - Accessible with your email software or over the web -- -- Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Following this bug reports from redhat
it rising some dangerous issue:
If on any reasons you data file is zeroed after some power
loss(it is the most known issue on XFS in the past) when you do
select count(*) from you_table you got zero if you table was in one 1GB(default) file or some other numbers !=count (*) from you_table before power loss
No errors, nothing suspicious in logs. No any checksum errors. Nothing.
Silent data loss is its pure form.
And thanks to all gods that you notice it before backup recycling
which contains good data.
Keep in mind it while checking you "backups" in any forms (pg_dump or the more dangerous and short-spoken PITR file backup)
You data is always in danger with "zeroed data file is normal
I'm running a streaming replication setup with PostgreSQL 9.5.2 and have started seeing these errors on a few INSERTs: ERROR: could not read block 8 in file "base/3884037/3885279": read only 0 of 8192 bytes on a few tables. If I look at that specific file, it's only 6 blocks long: # ls -la base/3884037/3885279 -
rw------- 1 postgres postgres 49152 May 30 12:56 base/3884037/3885279 It seems that this is the case on most tables in this state. I havn't seen any error on SELECT and I can SELECT * on the all tables I know have this problem. The database is machine is under reasonable load. On some tables an "ANALYZE tablename" causes the error. We recently had a streaming replication failover after loading a large amount of data with pg_restore. The problems seem to have started after that, but I'm not perfectly sure. I have data_checksums switched on so am suspecting a streaming replication bug. Anyone know of a recent bug which could have caused this? -- Brian Sutherland -- -- Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
I have a business plan for my product and services both developed on top of PostgreSQL. I am looking for partners to form a start-up to work on these product and services. My ideal candidates are PostgreSQL endorsers. In addition, I hope the technical details in my plan be exposed during the discussions in primitive stages as few as possible to potential competitors, non PostgreSQL endorsers in particular. As most predecessors did, I feel my idea unprecedented. However, I also understand that these days many people, including myself in most cases, tend to interpret terminologies like "business plan", "idea", "start-up", "cloud", "big data", etc. into "propaganda", "spam", or worse - "scam". This is why I not only draft the following targets to which I might send my solicitations, but also attach obvious concerns to them: - PostgreSQL mailing lists concerns: (a) Will my messages deemed as spam or harassment? (b) Which mailing list is appropriate for my messages if it really is? "-jobs" is definitely inappropriate because my pocket is empty and I am unable to hire anyone. - manually compiling the names and their associated e-mail addresses of core developers, hackers, contributers, users, etc. concerns: (a) This is a very ineffective approach. (b) I recall the horrible past that someone harvested years ago the e-mail addresses in mailing list archives and used them in a way I no longer remember now. That activity caused huge anger from many community members. - LinkedIn private message services concern: First I will have to invite many people I do not really know to link me in, then I ultimately fall into their black list. - LinkedIn interest groups concern: I have a feeling that many articles and discussions posted in the groups I joined are in essence propaganda coated with technology. - Twitter concerns: (a) People do not like advertisements. Such messages are most likely be ignored. (b) I have few followers. - Requesting for a new PostgreSQL mailing list, which might be called "-biz-opportunities" or "-biz-partners" concern: My messages will be delivered only to few recipients because new list will have only quite a few subscribers. Above all, the last result I want to get from my inquiries is *silence*. EnterpriseDB and Xtuple are two successful examples I heard of. Hopefully I will be able to follow their pattens of success. I wonder how they achieved them, such as: - How did those initiators find and attract in the first place those individuals who are willing to discuss their grreat plans? - How did they discuss their plans without fearing too many of their sensitive plan details exposed before their companies were formed? I need your enlightenment! What routes are the least offensive, yet most effective, efficient, and appropriate ones for me to take to have my awesome or yet another awful "idea" be delivered to those targeted PostgreSQL endorsers? Thank you in advance! Best Regards, CN -- http://www.fastmail.com - Or how I learned to stop worrying and love email again -- -- Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Hi all, i am about to begin with postgresql plugin development. Currently i'm trying to become somewhat familiar with the postgresql sources. Without going too deep into details about the plugin, i want to use many Oid to pointer relations. The pointer is a pointer to my own struct (allocated with palloc). There will be approx. 1000 unique oid/pointer pairs. Basically, what i want is, to be able to get the pointer to my struct by Oid. Is there is a suitable hashmap or key-value storage solution in the pg code? if so, please point me to the right part of the source. thanks, Attila Soki -- -- Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general