Re: Large scale reliable software system

Correct. It’s a tragically wrong piece of folk wisdom that’s pretty general across web development communities. > On Jun 26, 2023, at 21:32, Michael Nolan wrote: > > It's not just Ruby, dumb databases are preferred in projects like > WordPress, Drupal and Joomla, too. > > Now, if it's because

Re: Large scale reliable software system

It's not just Ruby, dumb databases are preferred in projects like WordPress, Drupal and Joomla, too. Now, if it's because they're used to using MySQL, well maybe that's not so hard to understand. :-) On Mon, Jun 26, 2023 at 8:05 PM Guyren Howe wrote: > > This is a reasonable answer, but I want

Re: Large scale reliable software system

This is a reasonable answer, but I want to offer a caveat. Likely because of the influence of the originator of Ruby on Rails, it is close to holy writ in the web development community that the database must be treated as a dumb data bucket and all business logic must be implemented in the Ruby

Re: Large scale reliable software system

On 6/26/23 16:48, B M wrote: Dear all, After greeting, I taught PostgreSQL myself and developed a small scale experimentalsoftware system using PostgreSQL in the back-end. I would like to know your advices to develop a large scale reliable software system using PostgreSQL in the back-end, t

Large scale reliable software system

Dear all, After greeting, I taught PostgreSQL myself and developed a small scale experimental software system using PostgreSQL in the back-end. I would like to know your advices to develop a large scale reliable software system using PostgreSQL in the back-end, through which i can share the stor

Re: bug or lacking doc hint

On Mon, Jun 26, 2023 at 4:05 PM Ron wrote: > On 6/26/23 07:22, Marc Millas wrote: > > > > On Mon, Jun 26, 2023 at 5:47 AM Avin Kavish wrote: > >> Sounds like the problem you are having is, the server is running out of >> temporary resources for the operation that users are trying to do. So >> ac

Re: Large pkey index on insert-only table

On Mon, Jun 26, 2023 at 8:50 AM Devin Ivy wrote: > Any thoughts on why this may be, or where to go next to continue tracking > this down? Also, could the primary key column order `(id, ancestor_id)` vs > `(ancestor_id, id)` significantly affect the index size depending on the > column cardinal

Large pkey index on insert-only table

Hi all, I have a suspiciously large index, and I could use a hand finding a root cause for its size. This index supports the primary key for a closure table that models threaded comments with columns `(id, ancestor_id, depth)`. The primary key is composite: `(id, ancestor_id)`. The id columns ar

Re: A question about the postgres's website

> On 24 Jun 2023, at 15:36, wen-yi wrote: > > Hi community, > When I check the postgres's website, I find something confused: > > https://www.postgresql.org/community/ (Quick Links: Don't see the slack item) > > https://www.postgresql.org/list/ (Quick Links: See the slack item) > > Can someone

Re: bug or lacking doc hint

On 6/26/23 07:22, Marc Millas wrote: On Mon, Jun 26, 2023 at 5:47 AM Avin Kavish wrote: Sounds like the problem you are having is, the server is running out of temporary resources for the operation that users are trying to do. So according to Tom, on the postgres side, the operati

Re: A question about the postgres's website

On 6/24/23 06:36, wen-yi wrote: Hi community, When I check the postgres's website, I find something confused: https://www.postgresql.org/community/ (Quick Links: Don't see the slack item) https://www.postgresql.org/list/

Re: bug or lacking doc hint

On Mon, Jun 26, 2023 at 5:47 AM Avin Kavish wrote: > Sounds like the problem you are having is, the server is running out of > temporary resources for the operation that users are trying to do. So > according to Tom, on the postgres side, the operation cannot be optimized > further. > > I think y

Re: PostgreSQL Commercial Support

On 6/26/23 05:56, Oduba, Ernest wrote: We want to start using PostgreSQL and we intent to have a commercial support. Kindly advise who can assist with this request for further engagement. See: https://www.postgresql.org/support/professional_support/ -- Joe Conway PostgreSQL Contributors Team

Re: How to show current schema of running queries in postgresql 13

po 26. 6. 2023 v 12:23 odesílatel 陈锡汉 napsal: > I have no way to force users doing this… > Then there is only one possible way - via custom extension you can catch the SET SEARCH_PATH statement, and you can do this. If you cannot use own extension, then there is not any way. > > > 回复的原邮

回复：How to show current schema of running queries in postgresql 13

I have no way to force users doing this… 回复的原邮件 | 发件人 | Pavel Stehule | | 日期 | 2023年06月26日 17:51 | | 收件人 | 陈锡汉 | | 抄送至 | pgsql-general@lists.postgresql.org | | 主题 | Re: How to show current schema of running queries in postgresql 13 | po 26. 6. 2023 v 9:19 odesílatel Pavel Stehule

Re: How to show current schema of running queries in postgresql 13

po 26. 6. 2023 v 9:19 odesílatel Pavel Stehule napsal: > Hi > > > > no, there is nothing for this purpose. > > you can use application_name > > so user can do > > SET search_path=MySchema; > SET application_name = 'MySchema'; > SELECT * FROM ... > > and application name is visible from pg_stat_ac

A question about the postgres's website

Hi community, When I check the postgres's website, I find something confused: https://www.postgresql.org/community/ (Quick Links: Don't see the slack item) https://www.postgresql.org/list/ (Quick Links: See the slack item) Can someone give me some advice? Thanks in advance! Yours, Wen Yi

Re: How to show current schema of running queries in postgresql 13

Hi po 26. 6. 2023 v 8:39 odesílatel 陈锡汉 napsal: > Hello,I use multi-schemas in one database in Postgres,such as > > ``` > Postgres(instance) > MyDB >public >MySchema1 > table1 > table2 >MySchema2 > table1 > table2 >MySchema3 > table1 > table2 > ```