[pgadmin-org/pgadmin4] 5a2287: Czech translation for version 7.4

[Libor M.]

  Branch: refs/heads/master
  Home:   https://github.com/pgadmin-org/pgadmin4
  Commit: 5a228761768f179aa5636acad4b05a20c780f07d
  
https://github.com/pgadmin-org/pgadmin4/commit/5a228761768f179aa5636acad4b05a20c780f07d
  Author: Libor M 
  Date:   2023-06-26 (Mon, 26 Jun 2023)

  Changed paths:
M web/pgadmin/translations/cs/LC_MESSAGES/messages.mo
M web/pgadmin/translations/cs/LC_MESSAGES/messages.po

  Log Message:
  ---
  Czech translation for version 7.4

[pgadmin-org/pgadmin4] ee0cfe: Chinese translation for v7.4

[MysticBoy]

  Branch: refs/heads/master
  Home:   https://github.com/pgadmin-org/pgadmin4
  Commit: ee0cfef31a7cef07af39163aae771ce8eb40bff6
  
https://github.com/pgadmin-org/pgadmin4/commit/ee0cfef31a7cef07af39163aae771ce8eb40bff6
  Author: MysticBoy 
  Date:   2023-06-26 (Mon, 26 Jun 2023)

  Changed paths:
M web/pgadmin/translations/zh/LC_MESSAGES/messages.mo
M web/pgadmin/translations/zh/LC_MESSAGES/messages.po

  Log Message:
  ---
  Chinese translation for v7.4

[pgadmin-org/pgadmin4] 64c48a: Indonesian translation for version 7.4

[oon arfiandwi]

  Branch: refs/heads/master
  Home:   https://github.com/pgadmin-org/pgadmin4
  Commit: 64c48ad237d41906b0665999b710348d28af7cf3
  
https://github.com/pgadmin-org/pgadmin4/commit/64c48ad237d41906b0665999b710348d28af7cf3
  Author: oon arfiandwi 
  Date:   2023-06-26 (Mon, 26 Jun 2023)

  Changed paths:
M web/pgadmin/translations/id/LC_MESSAGES/messages.mo
M web/pgadmin/translations/id/LC_MESSAGES/messages.po

  Log Message:
  ---
  Indonesian translation for version 7.4

Re: Adding storage parameters on index

[Akshay Joshi]

Hi Pravesh

On Fri, Jun 23, 2023 at 2:28 PM Pravesh Sharma <
pravesh.sha...@enterprisedb.com> wrote:

> Hi All,
>
> I am working on feature #6374
>  which is
> adding storage parameters while creating an index. I have made changes in
> the definition tab of create index to have all the required parameters.
> Attached is the new design, please review it.
>
> I also have a few points which require suggestions.
>
>1. Storage parameters are different for different access methods. If
>an access method does not support a parameter we can either disable it or
>hide it (I am thinking of hiding it based on the access method).
>
>Disable the controls.

>
>1. There is a storage parameter named *buffering *which is by
>default auto and takes on/off value. What type of control should I use for
>it? Should it be a switch or a drop down with three options on, off and
>auto, if we have a switch user won't be able to move to auto.
>
> It should be a drop-down with all three options.

>
>1. There is a parameter *vacuum_cleanup_index_scale_factor *that was
>added on PostgreSQL 11 but was removed on PostgreSQL 13, should we add this
>too?
>
> No need to add the above parameter.

>
>
> Thanks
> Pravesh Sharma
>
> --
>
> 
>
> Pravesh Sharma
>
> Software Engineer
>
> +91 9406461406
>
> www.enterprisedb.com
>
> Power to Postgres
>
> 
> 
> 
> 
>

Re: Adding storage parameters on index

[Aditya Toshniwal]

Hi,

I would also suggest moving Columns and Include Columns to a separate tab -
Columns.

On Mon, Jun 26, 2023 at 11:19 AM Akshay Joshi 
wrote:

> Hi Pravesh
>
> On Fri, Jun 23, 2023 at 2:28 PM Pravesh Sharma <
> pravesh.sha...@enterprisedb.com> wrote:
>
>> Hi All,
>>
>> I am working on feature #6374
>>  which is
>> adding storage parameters while creating an index. I have made changes in
>> the definition tab of create index to have all the required parameters.
>> Attached is the new design, please review it.
>>
>> I also have a few points which require suggestions.
>>
>>1. Storage parameters are different for different access methods. If
>>an access method does not support a parameter we can either disable it or
>>hide it (I am thinking of hiding it based on the access method).
>>
>>Disable the controls.
>
>>
>>1. There is a storage parameter named *buffering *which is by
>>default auto and takes on/off value. What type of control should I use for
>>it? Should it be a switch or a drop down with three options on, off and
>>auto, if we have a switch user won't be able to move to auto.
>>
>> It should be a drop-down with all three options.
>
>>
>>1. There is a parameter *vacuum_cleanup_index_scale_factor *that was
>>added on PostgreSQL 11 but was removed on PostgreSQL 13, should we add 
>> this
>>too?
>>
>> No need to add the above parameter.
>
>>
>>
>> Thanks
>> Pravesh Sharma
>>
>> --
>>
>> 
>>
>> Pravesh Sharma
>>
>> Software Engineer
>>
>> +91 9406461406
>>
>> www.enterprisedb.com
>>
>> Power to Postgres
>>
>> 
>> 
>> 
>> 
>>
>

-- 
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*

"Don't Complain about Heat, Plant a TREE"