Re: PostgreSQL and local HDD

On 8/15/23 23:48, Olivier Gautherot wrote: El mié, 16 ago 2023 5:39, Ron escribió: On 8/15/23 04:24, Olivier Gautherot wrote: [snip] Does the database have to be on a storage like EMC or QNAP? Faster storage can only help but I would start by discarding functional

Re: PostgreSQL and local HDD

El mié, 16 ago 2023 5:39, Ron escribió: > On 8/15/23 04:24, Olivier Gautherot wrote: > > [snip] > > Does the database have to be on a storage like EMC or QNAP? >> > > Faster storage can only help but I would start by discarding functional > overhead. > > > Functional overhead? > I mean

Re: PostgreSQL and local HDD

On 8/15/23 02:23, Jason Long wrote: [snip] Does PostgreSQL have an option to increase speed? Like a Turbo button? -- Born in Arizona, moved to Babylonia.

Re: PostgreSQL and local HDD

On 8/15/23 04:24, Olivier Gautherot wrote: [snip] Does the database have to be on a storage like EMC or QNAP? Faster storage can only help but I would start by discarding functional overhead. Functional overhead? -- Born in Arizona, moved to Babylonia.

Re: Cast INTEGER to BIT confusion

On Tue, Aug 15, 2023 at 4:49 AM [Quipsy] Markus Karg wrote: > > CREATE TABLE T (c BIT); > > INSERT INTO T VALUES (1); > > -- I MUST NOT change both lines in any way as these are part of a > third-party application! > That is quite the requirement! I hope that the rest of the application is more

Re: Converting sql anywhere to postgres

On 2023-08-15 18:43:11 +0200, Georg H. wrote: > update mytest.autovalues set product='pear', updated_by=DEFAULT where key=2; Oh, I didn't know that worked. Obvious in hindsight, of course (I've been using DEFAULT in VALUES(...) for

Re: PostgreSQL and GUI management

På tirsdag 15. august 2023 kl. 22:52:48, skrev Rob Sargent < robjsarg...@gmail.com >: […] All the nice buzzwordy things: dashboards, alarm bells, point-and-click drop downs for config values (with tool tip descriptions of what they might do), coffee dispenser.

Re: Converting sql anywhere to postgres

I’m fairly confident you can do this using a Rule. It would even be fairly simple. Be careful, though: Rules are Postgres’ biggest potential foot gun. Guyren G Howe On Aug 15, 2023 at 08:05 -0700, Russell Rose | Passfield Data Systems , wrote: > Hi there > > I am trying to convert a SQL

Re: PostgreSQL and GUI management

On 8/15/23 13:52, Rob Sargent wrote: On 8/15/23 12:57, Adrian Klaver wrote: On 8/15/23 11:43, Rob Sargent wrote: On 8/15/23 12:38, Adrian Klaver wrote: On 8/15/23 08:08, Jason Long wrote: Hello, Does PostgreSQL have a graphical environment for management or is it only managed through CLI?

Re: PostgreSQL and GUI management

On 8/15/23 12:57, Adrian Klaver wrote: On 8/15/23 11:43, Rob Sargent wrote: On 8/15/23 12:38, Adrian Klaver wrote: On 8/15/23 08:08, Jason Long wrote: Hello, Does PostgreSQL have a graphical environment for management or is it only managed through CLI? There are, but make your life easier

Re: PostgreSQL and GUI management

út 15. 8. 2023 v 20:38 odesílatel Adrian Klaver napsal: > On 8/15/23 08:08, Jason Long wrote: > > Hello, > > Does PostgreSQL have a graphical environment for management or is it > > only managed through CLI? > > There are, but make your life easier and learn to use psql: > >

Re: PostgreSQL and GUI management

On 8/15/23 11:43, Rob Sargent wrote: On 8/15/23 12:38, Adrian Klaver wrote: On 8/15/23 08:08, Jason Long wrote: Hello, Does PostgreSQL have a graphical environment for management or is it only managed through CLI? There are, but make your life easier and learn to use psql:

Re: PostgreSQL and GUI management

På tirsdag 15. august 2023 kl. 20:43:16, skrev Rob Sargent < robjsarg...@gmail.com >: […] Adrian, Much as I love it, psql is not what I would call a management tool? We have a multi-terabyte cluster in production which we manage using psql. Locally I use IntelliJ

Re: PostgreSQL and GUI management

On 8/15/23 12:38, Adrian Klaver wrote: On 8/15/23 08:08, Jason Long wrote: Hello, Does PostgreSQL have a graphical environment for management or is it only managed through CLI? There are, but make your life easier and learn to use psql: https://www.postgresql.org/docs/current/app-psql.html

Re: PostgreSQL and GUI management

On 8/15/23 08:08, Jason Long wrote: Hello, Does PostgreSQL have a graphical environment for management or is it only managed through CLI? There are, but make your life easier and learn to use psql: https://www.postgresql.org/docs/current/app-psql.html It ships with Postgres and runs close

Re: Converting sql anywhere to postgres

The timestamp default in Sql Anywhere is quite easy to convert with a trigger as I can check the old and new values and if they are the same then update. It is very unlikely that the application will manually set a timestamp that is identical to the value stored. This is not the case with a

Re: AW: PostgreSQL and GUI management

Hello,Thank you so much for your reply.Is it free?Has it met all your needs? Sent from Yahoo Mail on Android On Tue, Aug 15, 2023 at 6:40 PM, [Quipsy] Markus Karg wrote: I am using pg_admin in the browser, and it works rather fine for me. -Markus   Von: Jason Long Gesendet:

Re: Converting sql anywhere to postgres

On 8/15/23 09:43, Georg H. wrote: Hi, Am 15.08.2023 um 17:04 schrieb Russell Rose | Passfield Data Systems: Hi there I am trying to convert a SQL Anywhere database to postgres. Within SQL anywhere a field can have a default value of ‘last user’. This means that when you perform an update

Re: Converting sql anywhere to postgres

Hi, Am 15.08.2023 um 17:04 schrieb Russell Rose | Passfield Data Systems: Hi there I am trying to convert a SQL Anywhere database to postgres. Within SQL anywhere a field can have a default value of ‘last user’. This means that when you perform an update on a table, if the field is not

Re: Converting sql anywhere to postgres

> On 15/08/2023 17:04 CEST Russell Rose | Passfield Data Systems > wrote: > > I am trying to convert a SQL Anywhere database to postgres. Within SQL > anywhere a field can have a default value of ‘last user’. This means that > when you perform an update on a table, if the field is not explicitly

Re: Converting sql anywhere to postgres

On 8/15/23 08:04, Russell Rose | Passfield Data Systems wrote: Hi there I am trying to convert a SQL Anywhere database to postgres. Within SQL anywhere a field can have a default value of ‘last user’. This means that when you perform an update on a table, if the field is not explicitly set

Re: PostgreSQL and GUI management

Am 15.08.23 17:08 schrieb(en) Jason Long: Hello,Does PostgreSQL have a graphical environment for management or is it only managed through CLI? Have a look at DBeaver – I use the Eclipse plug-in, but there are stand-alone (free) versions, too. Hth, Albrecht.

Re: PostgreSQL and GUI management

út 15. 8. 2023 v 17:16 odesílatel Pavel Stehule napsal: > Hi > > út 15. 8. 2023 v 17:09 odesílatel Jason Long napsal: > >> Hello, >> Does PostgreSQL have a graphical environment for management or is it only >> managed through CLI? >> > >

Re: PostgreSQL and GUI management

Hi út 15. 8. 2023 v 17:09 odesílatel Jason Long napsal: > Hello, > Does PostgreSQL have a graphical environment for management or is it only > managed through CLI? > https://wiki.postgresql.org/wiki/Community_Guide_to_PostgreSQL_GUI_Tools Regards Pavel > > Thank you. >

AW: PostgreSQL and GUI management

I am using pg_admin in the browser, and it works rather fine for me. -Markus Von: Jason Long Gesendet: Dienstag, 15. August 2023 17:09 An: pgsql-general@lists.postgresql.org Betreff: PostgreSQL and GUI management Hello, Does PostgreSQL have a graphical environment for management or is it only

PostgreSQL and GUI management

Hello,Does PostgreSQL have a graphical environment for management or is it only managed through CLI? Thank you.

Converting sql anywhere to postgres

Hi there I am trying to convert a SQL Anywhere database to postgres. Within SQL anywhere a field can have a default value of 'last user'. This means that when you perform an update on a table, if the field is not explicitly set then the current user is used. So for instance if I have a field

Re: AW: Cast INTEGER to BIT confusion

> On 15/08/2023 14:02 CEST [Quipsy] Markus Karg wrote: > > I just tried out your proposal on PostgreSQL 15.3 and this is the result: > > ERROR: column "c" is of type bit but expression is of type integer > LINE 5: INSERT INTO t VALUES (1); > ^ > HINT: You will

Re: AW: Cast INTEGER to BIT confusion

> On 15/08/2023 13:59 CEST [Quipsy] Markus Karg wrote: > > Is setting the search path something that has to be done for each new > connection / each user, or is this something static and global for the > database? The search path is set per connection and the initial search path can be

Re: Query plan regression between CTE and views

I'm on PostgreSQL 15 with essentially a stock configuration. On Tue, Aug 15, 2023 at 8:58 AM Ron wrote: > > On 8/14/23 09:54, David Gilman wrote: > > I have a query that was originally written as a handful of CTEs out of > > convenience. It is producing a reasonable query plan because the CTE >

AW: Cast INTEGER to BIT confusion

Erik, I just tried out your proposal on PostgreSQL 15.3 and this is the result: ERROR: column "c" is of type bit but expression is of type integer LINE 5: INSERT INTO t VALUES (1); ^ HINT: You will need to rewrite or cast the expression. Apparently the search

AW: Cast INTEGER to BIT confusion

Thank you, Erik! Prefixing the search path in fact looks very interesting, and I think in this particular application it is a safe (and the only) solution. Is setting the search path something that has to be done for each new connection / each user, or is this something static and global for

Re: Cast INTEGER to BIT confusion

> On 15/08/2023 10:49 CEST [Quipsy] Markus Karg wrote: > > Hello PostgreSQL Community, > > I like to store just a single bit but that can be either 1 or 0, so I tried > to do this: > > CREATE TABLE T (c BIT); > INSERT INTO T VALUES (1); > -- I MUST NOT change both lines in any way as these are

Re: PostgreSQL and local HDD

Hi Jason On Tue, Aug 15, 2023 at 9:23 AM Jason Long wrote: > Hello, > Why is the PostgreSQL database slow when it is on the server's hard drive? > My servers are HPE ProLiant DL380p G8 and HPE ProLiant DL380 G9. > Can you be more specific in your question? Reasons for the server would be

Cast INTEGER to BIT confusion

Hello PostgreSQL Community, I have 25+ years of experience with some other RDBMS, but I am a PostgreSQL starter, so I assume the following is rather a simple beginner's question...: I like to store just a single bit but that can be either 1 or 0, so I tried to do this: CREATE TABLE T (c BIT);

PostgreSQL and local HDD

Hello, Why is the PostgreSQL database slow when it is on the server's hard drive? My servers are HPE ProLiant DL380p G8 and HPE ProLiant DL380 G9. Does the database have to be on a storage like EMC or QNAP? Does PostgreSQL have an option to increase speed? Thank you.